Managing User Permissions and Roles

Our platform offers several different permission levels that you can assign to users depending on what level of access they need. The basic roles include Viewer which allows read-only access, Editor which allows creating and modifying content, Admin which has full access except for billing, and Owner which has complete control including billing and account deletion.

To change someone's role, you should go to the Team section and find the user you want to update, then click on their name or the dropdown menu next to their name depending on your screen size, and select the new role from the options that appear, then make sure to click Save or the changes won't take effect, although sometimes the changes save automatically but not always so it's better to look for a Save button just in case.

When you're adding a new team member, you can either send them an invitation email by entering their email address in the invite field, or you can generate a shareable invite link that anyone can use to join your team, or if you have SSO enabled you can have them sign in through your identity provider and they'll automatically be added with whatever default role you've configured in your SSO settings.

If you need to remove someone's access, you can either deactivate their account which preserves their data and history but prevents them from logging in, or you can fully delete their account which removes all their data and is permanent and can't be undone, or you can just change their role to Viewer which technically keeps them in the system but limits what they can do.

There are also some advanced permission settings you can configure if you need more granular control. You can restrict access to specific projects by going to the project settings and adding or removing team members from the access list, and you can control whether users can export data by toggling the export permission in their user profile, and you can limit who can create new projects by setting the project creation permission to Admin-only in your organization settings, and you can control API access separately from dashboard access if you want to give someone API credentials without letting them log into the web interface.

Keep in mind that permission changes take effect immediately when you save them, so if you remove someone's access they'll be logged out right away, and if you're changing permissions for multiple users you should do it one at a time or use the bulk actions menu if you're changing everyone to the same role, but the bulk actions only work for changing roles not for other permission settings.