Access Rights, Teams & User Management
Last updated
Was this helpful?
Last updated
Was this helpful?
Flagship offers an intuitive way to manage teams and members' roles and rights, giving you complete control and flexibility over your organization's access and control.
In this guide, we will walk you through how to manage the roles and rights of your teams at the account and project levels.
Managing Roles and Rights at the Account Level
At the account level, you can manage roles and rights for teams and seats (users). Teams are groups of users that can be assigned to different projects, while seats are the available spots on a team. This means you can have multiple teams, each with a different set of members, and each member can have different rights depending on the team they belong to.
Flagship allows users to manage their accounts with different user roles and rights, ensuring optimal collaboration and preventing usage conflict. Here is an overview of the user roles, rights, and how to manage them.
There are five types of account roles: Account Owner, Super Admin, Project Manager, Member, and Guest. Each role has different rights and privileges.
Account Owner: The Account Owner has the highest level of access and can add, edit or remove team members from different projects. They also have full user rights, including billing (the billing part is valid for Premium Subscription only).
Super Admin: Super Admins have access to all projects and can configure them. The Super Admin role has full user rights in every environment, with the exception of not being able to access the billing details.
Project Manager: Project Managers can add new users and assign them roles. They have full rights to the assigned projects except create, rename or delete them.
Member: Members have limited access rights and can access projects, but may not be able to configure them unless they have accessed the project roles that allow them to do so.
Guest: Guests have limited access rights and can access projects, but may not be able to configure them unless they have accessed the project roles that allow them to do so. The "guest" role has the lowest access level and no rights on changing account parameters.
To create and manage teams and seats, go to the "Teams" page accessible from Settings. From there, you can view all your teams and seats and edit their settings as needed.
When you reach this page, you will see the Teams section. Here, you can use the search bar and filtering options to search for teams, create a new team by clicking on the CTA, or edit existing teams, both of which will open a window where a team name can be entered or replaced and Team Members section to add members to the team by typing their names or emails and delete them from the team.
In the Seats section, you can search for members using the search bar and filtering options, add new members by clicking on the CTA, and view members with their names, emails, roles, MFA method, teams they are part of, and projects they are part of. A three-dot icon next to each member line opens a drop-down list with options: edit roles, see projects, and remove. The “Edit Roles” option, when clicked, opens a window that allows users to switch roles between Account Owner, Tech Manager, Project Manager, Member, and Guest. The “See Projects” option allows users to view projects accessible to the member.
To get started, navigate to the Teams tab by clicking on "Teams" in the left lateral navigation.
To create a new team, click on the "Create Team" button located on the right side, above the Teams tab. Enter the team name.You can create several teams in your account, and in each team you’ll be able to add users.
You can only add users which were already added in Seats.
Next, in the "Members" area enter the email addresses of the users you want to add. Note that you can only add users who have already been added in "Seats".
After you've added members to a team, you can assign the team to a project. To do this, go back to the Teams tab and select the team you want to assign. Then, click on the "Assign to Projects" button and select the project(s) you want to assign the team to.
You can also edit an existing team's name and members. To do this, click on the team you want to edit and click the "Edit" button. Make your changes and click "Save".
Step 6: Delete a Team
If you need to delete a team, click on the team you want to delete and click the "Delete" button. Note that deleting a team will also remove the project access of all users belonging to that team.
💡 Good to know
Once you did that, you’ll be able to directly add a team to a project from the dashboard. You can also delete a team, but beware, deleting a team will also remove the project access of all users belonging to those teams.
To add members to a seat or team, click on the "Add Member" button and enter the member's email address. You can also assign roles and rights to each member.
To add a user, you can follow those steps:
Go to Teams > Seats tab using the lateral navigation
Click on Add user
Enter the Email address and the [role] you want to give that user
Validate the form, the user will receive an email.
To remove a user, follow these steps:
Go to Teams > Seats tab using the lateral navigation
Each user is managed separately – click on the 3 vertical dots and click on Remove option
A prompt appear to remind you that this action will completely remove that user from all projects and all environments
Validating the prompt delete the user
❗Caution: Teammates who leave your company should have their Flagship user rights deleted as part of their off-boarding. Allowing former employees to retain access and user rights to the Flagship platform creates risk for your company, especially if they were admins. Flagship by AB Tasty is not responsible for the mismanagement of access to the platform.
To edit a user’s rights, follow these steps:
Go to Teams > Seats tab using the lateral navigation
Each user is managed separately – click the 3 vertical dots and click edits
A drop-down appears to select the role you wish to assign this user: - Select the preferred user type with the dropdown and confirm by clicking on the CTA - Click the cross to cancel
A validation message appears confirming this user’s rights have been edited
If the user is currently connected to the platform, the new rights will be operational at the next refresh of the page.
The following table lists the rights associated with each role.
Action
Account Owner
Super Admin
Project Manager
Member
Guest
Can access Account settings
✅
✅
✅
✅
❌
Can edit Account Settings
✅
✅
❌
❌
❌
Can access Teams/Seats
✅
✅
✅
✅
✅
Can add/edit/delete a Team
✅
✅
❌
❌
❌
Can add/edit a user
✅
✅
✅
❌
❌
Can access Platforms Integrations
✅
✅
✅
✅
❌
Can edit Platforms Integrations
✅
✅
❌
❌
❌
Access/Enable/Disable Panic Mode
✅
✅
❌
❌
❌
Can Create/Edit/Delete Environment
✅
✅
❌
❌
❌
Action
Account Owner
Super Admin
Project Manager
Member
Guest
Can access Environment settings
✅
✅
✅
✅
❌
Can edit Environment Settings
✅
✅
❌
❌
❌
Can see sensitive info (API Keys, IDs)
✅
✅
❌
❌
❌
Action
Account Owner
Super Admin
Project Manager
Member
Guest
Can delete an archived use case
✅
✅
✅
❌
❌
Can create/edit/delete an archived folder
✅
✅
✅
❌
❌
Can move an archived use case to another folder
✅
✅
✅
❌
❌
The following table lists the rights associated with each role.
Action
Account Owner
Super Admin
Project Manager
Member
Guest
Admin
User
Viewer
Can create project
✅
✅
✅
Can't see projects by default
Can't see projects by default
❌
❌
❌
Can rename/delete project
✅
✅
✅
Can't see projects by default
Can't see projects by default
❌
❌
❌
Can view members on project
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
✅
✅
Can add members on project
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
❌
❌
Can edit/delete members on project
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
❌
❌
Can launch/pause a project
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
❌
❌
Can create a use case
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
✅
❌
Can edit a use case not launched
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
✅
❌
Can edit a use case launched
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
✅
❌
Can delete a use case
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
✅
❌
Can duplicate a use case
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
✅
❌
Can access to the details
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
✅
✅
Can access to the report
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
✅
✅
Can launch/pause a use case
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
✅
❌
Can archive a use case not launched
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
✅
❌
Can archive a use case launched
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
❌
❌
Can access archived use cases
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅
✅
✅
Can move a use case to another project
✅
✅
✅
Can't see projects by default
Can't see projects by default
✅ if admin access to both project
❌
❌