Every so often, our Vice President of Product shares an email with the company that tells the background story on why Brightspot’s features are the way they are. Not one to keep secrets, we’re sharing her insights with you here, in a series called “Inside Brightspot.” From creating users and permissions to knowing the difference between different dashboard widgets, this series will answer the questions anyone who publishes digital content has likely pondered.
In addition to covering the history of Brightspot permissions and the modern permissions system, let's next cover some of the "extra" settings that are available as part of Brightspot's permissions system.
Under the Permissions Settings, Brightspot also supports Site-Specific Permissions.
These are helpful in cases where a team wants a given Role to have additional permissions on a given site.
Take an Editor Role that gives access to edit and publish Articles and Galleries. That same Role might be responsible for editing and updating the homepage on another site. In this situation, the Site-Specific Permissions can be used. Think of these permissions as additive to the overall, primary permissions settings.
Below the Permissions Settings, you'll also see an area in the UI to associate Content Templates with a Role. If you aren't familiar with Brightspot's Content Templates, they function as shortcuts to pre-populate a content type with data.
This one is is obvious: this is where an admin user can create a custom dashboard for a given Role. An admin user can also configure the content types and contents that this role will see in the Quick Start Widget in this area.
The most critical setting in this area is two-factor authentication. An admin user can turn this setting on to require that everyone associated with this Role use two-factor authentication when logging into Brightspot.
This area can be used to create and manage notifications settings for a given Role. An admin user can set a delivery option (i.e. whether notifications are delivered via Slack, email, text or browser), as well as subscriptions (i.e., what a given role is going to get notifications about). This is helpful for admin users because it allows them to manage notification preferences for an entire group of users.
Maybe the best setting on permissions is the Advanced / Gear setting on Roles. Clicking it will reveal a set of choices, which include creating a brand new Role, or copying the current Role. It also will expose the editing history of a given Role, allowing insight into changes that have been made over time.
The Gear area wasn't a feature that was included in earlier versions of the system. It's an incredibly useful tool on content, so we felt it was critical to add for the benefit of admin users as well, giving them the ability to save time and resources via a quick copy action of an existing Role.