In this section
Resources / Help / Teams
Roles and permissions
The built-in roles in Hubbo, what each can do by default, and how to adjust their permissions.
Every team member has one role. A role is a set of permissions, and each permission names an action on an area of the product, such as update:notification or read:road-map. You can review and change them under Settings → Team → Roles and Permissions.
Areas and actions
Areas: notification, message (Messages), survey, nps, road-map, status, settings, appearance, team and bug. Actions: create, read, update and delete (appearance has the same four).
Default roles
| Role | Default access |
|---|---|
| Administrator | Full access to every area, including team and settings. |
| Manager | Full access to the team. Read access to notifications, Messages, surveys, NPS, roadmap, status, settings and appearance. |
| Writer | Create, edit and delete notifications, messages, surveys, NPS and roadmaps. Read access to team, appearance and status. |
| Designer | Create, edit and delete appearance. Read access to the other areas. |
| Guest | Read-only access to notifications, surveys, NPS, roadmap, status and appearance. No access to team or Messages. |
| Support | Create, edit and delete messages, status and roadmap. Read access to notifications, surveys, NPS, appearance and team. |
The account owner is the person who created the account. Their role is fixed.
How restrictions show up
- Areas a role cannot read are hidden, or the page redirects to a place they can view.
- Buttons for actions a role cannot perform are disabled, with a tooltip such as “You are not permitted to perform this action”.
- Permissions are checked on the server too, so hiding a button is not the only protection.
Bug permissions
The role list includes bug permissions. The bug report product is not available yet (coming soon), so these permissions do nothing for now.
Recommendations
- Give people the least access they need. Most editors only need Writer.
- Use Designer for brand or front-end people who should change colors but not publish content.
- Use Guest for stakeholders who just want to see what is going on.
- Review your team list when people leave.