Copyright © RebelMouse 2019

Follow Us:

Account Dashboard

Here at RebelMouse, we understand that every editorial team is structured differently. Whether you operate your web property with one editor, or have a network of 1,000+ contributors, it’s easy to manage your team through the RebelMouse platform.


To easily add (or remove) individuals to the platform click 'Accounts' in the left admin panel OR type in YourDomain/core/dashboard/sites:


Invite individuals to join the platform via email, while selecting that individual’s respective role within your web property:


User Permission Levels

Administrator:  An Administrator has full control, access, and permissions across the entire web property. These controls include:
- Creating, publishing and deleting content
- Posting content to linked social accounts
- Accessing the Layout & Design tool
- Viewing the stats dashboard
- Accesing the property’s account section


Editor:  An Editor has the same access and permissions of an Administrator, with the exception of:
- They don't have the ability to publish content to your property’s linked social accounts (ie, Facebook & Twitter).
- They can't access the Layout & Design tool.


Guest Editor: A Guest Editor can edit a draft, but not publish the content. They cannot access administrative tools such as Sections, Layout& Design, Content Sources, or Account.


Guest Writer:  A Guest Writer can draft, but not publish content. They cannot access administrative tools such as Sections, Layout& Design, Content Sources, or Account.


Read Only:  A Read Only user can only access the Stats dashboard. They cannot draft or publish content to the web property, access the Layout and Design tool, publish content to social, or access any administrative tools.


Developer: A Developer only has access to the Layout & Design tool. That way they can implement ads, edit the layout or change the design without creating or publishing any content in the site.


Community Member:  An admin can add anyone they want as a Community Member, and the Community user then can create their own personal profile/account page.
A Community Member can create and publish content directly to their personal account/profile page, though this content will not be featured on the property unless it is featured on a home or section page by an Administrator/Editor. Content published by a Community Member is accessible via the post/article’s direct URL.

Publishers No Longer Have to Submit Their Site to Google News

Google's Publisher Center creates new opportunities for audience growth

Just before the start of the next decade, Google announced an important change to its Google News offering with the launch of Google Publisher Center. The new interface merges Google News Producer and Google News Publisher into one to streamline the partnership process for publishers.

Overall, the change should make it easier for publishers to manage their Google News settings, including updating themes, directing URLs to section pages, and configuring user permissions. Read the full list of features here.

Keep reading... Show less

How to Find Work-Life Balance as a Remote Employee

Tips from our CEO on making the most of an office-free lifestyle

Working from home is becoming increasingly popular, with an estimated 66% of companies now allowing remote work and 16% operating completely office-free. RebelMouse is one of those fully remote companies, and over the years we've mastered how to stay close to each other despite being spread across more than a dozen countries. We believe working remotely is good for both our personal lives and our productivity. Read more about this here.

Still, working free from the shackles of an office environment doesn't mean every day is a dance party in your pajamas from 9 to 5. Working from home comes with its own set of challenges just like any other job.

Keep reading... Show less

Inside RebelMouse’s Quality Assurance Operations

How We've Perfected Stress-Free Publishing

At RebelMouse, we like to refer to our enterprise publishing platform as "lean tech." Most publishers have a natural inclination to start doubling down on teams of developers who try to build unique experiences to help stand out above the noise. But they should actually be doing the opposite: Lean tech is the preferred way to cut through content saturation. By allowing RebelMouse to obsess over your product, content producers, editors, managers, and everyone in between can focus on creating quality content and taking advantage of opportunities to leverage distributive publishing strategies that create real revenue growth.

One of the major reasons we're able to maintain a lean tech environment is thanks to our approach to quality assurance (QA). We make updates to our platform daily to ensure our clients always have access to the most robust, high-performing, and secure version of our platform. Behind the scenes, this means having a solid QA structure that's efficient, creates less bugs, and catches the ones that do pop up before they go live. It's a system of checks and balances that's hard and costly to replicate on a custom CMS. Here's a glimpse into how it works.

Our Tech Stack Toolbox

  • Cucumber
  • Java
  • Junit
  • Maven
  • Selenium WebDriver
  • TeamCity
  • Zalenium (Selenium Grid)

Our Checks and Balances Workflow

Automated Regression Testing Cycle

The Lifecycle of a Product Update

When an update is first made to RebelMouse, TeamCity immediately triggers the start of automated tests to review integrity.

TeamCity Build

TeamCity Agent

The tests run in parallel on TeamCity's Build Agent. Next, Zalenium creates docker containers with browsers that matches the count of parallel threads. An Allure report is then generated from the test results, which shows the state of the application after the update.

Allure Report Pass

If a test doesn't complete successfully, the testing framework receives a video with a failed test and attaches it to the Allure report.

Allure Report Issue

Based on the report analysis, a QA specialist will create a "bug" ticket in our product management software to address the issue if needed. Then, information about the bug is immediately sent to the project manager and we begin the process of correcting the problem.

The media powerhouses we power can publish with confidence knowing that any product issues that arise are met with a tried-and-true process to fix the problem with little-to-no disturbance to their workflow. If you have any questions about this process, please email

Related Articles

Subscribe to Our Newsletter