Source: https://fyno.docs.pageloop.ai/documentation/settings/workspace-settings/team

# Team

## Team Management and Access Control in Workspace

Team is a structure that Fyno built for you to work and collaborate effortlessly with your colleagues / teammates. But in order to understand how the Team function works, we will first need to understand what a Workspace is and how that functions. Read more here. The structuring and functioning of a Team works based on roles and policies assigned to each team member.

On signing up and creating a new account with Fyno, your Default Workspace is created and the registered email ID becomes the Organisation Owner.
![](/images/workspace-setting-team.png)

### What you can do with Teams

Team(s) allow you to:

- Provide restricted access to individual employees as per their role requirements.
- Have a centralized view of the team members along with their access levels and details.
- Collaborate easily with colleagues on projects and tasks within the Fyno application.

### How Access Control Works

![](/images/rolebase-add-on-policy.png)

Access in Fyno is managed using two layers:

- Roles (Base Access): Every user is assigned a role that defines their default level of access across the platform.

- Add-On Policies (Additional Access): Add-on policies allow you to grant specific capabilities on top of a role. This helps avoid assigning broader roles when only limited additional access is required. This is optional and can be used only when additional permissions are needed.

Add-on policies can be assigned:

- During user invitation.
- While modifying an existing user.

This enables flexible and controlled access management across teams.

### Roles

The below roles with unique levels of access have been created so that you can assign relevant roles to each person, based on what they need to access.
![](/images/campaign-manager-role-screenshot.png)

### Roles & Permissions

{\`
:root {
  \--rb-table-bg: #FFFFFF;
  \--rb-table-text: #1a1a1a;
  \--rb-header-bg: #F0F0F0;
  \--rb-header-text: #333333;
  \--rb-border-main: #E0E0E0;
  \--rb-border-sub: #F0F0F0;
  \--rb-category-bg: #FAF4E3;
  \--rb-category-text: #8B6602;
  \--badge-yes-bg: #F2F7E3;
  \--badge-yes-text: #547100;
  \--badge-view-bg: #E5EDF7;
  \--badge-view-text: #0E3672;
  \--badge-test-bg: #FAF4E3;
  \--badge-test-text: #8B6602;
  \--badge-no-bg: #F0F0F0;
  \--badge-no-text: #333333;
}
@media (prefers-color-scheme: dark) {
  :root {
    \--rb-table-bg: #121212;
    \--rb-table-text: #F0F0F0;
    \--rb-header-bg: #333333;
    \--rb-header-text: #F0F0F0;
    \--rb-border-main: #333333;
    \--rb-border-sub: #262626;
    \--rb-category-bg: #8B6602;
    \--rb-category-text: #FAF4E3;
    \--badge-yes-bg: #547100;
    \--badge-yes-text: #F2F7E3;
    \--badge-view-bg: #0E3672;
    \--badge-view-text: #E5EDF7;
    \--badge-test-bg: #8B6602;
    \--badge-test-text: #FAF4E3;
    \--badge-no-bg: #333333;
    \--badge-no-text: #F0F0F0;
  }
  tr td {
    background-color: var(--rb-table-bg, #121212) !important;
  }
}

/\* Custom CSS Tooltip Logic with speech bubble arrow pointer \*/
.tooltip-container {
  position: relative;
  display: inline-flex;
  align-items: center;
  margin-left: 6px;
  cursor: pointer;
  vertical-align: middle;
}
.tooltip-icon {
  color: currentColor; /\* Inherits text color of parent badge \*/
  opacity: 0.8;
  font-size: 10px;
  border: 1px solid currentColor;
  border-radius: 50%;
  width: 13px;
  height: 13px;
  display: inline-flex;
  align-items: center;
  justify-content: center;
  font-weight: bold;
  font-style: normal;
}
.tooltip-text {
  visibility: hidden;
  opacity: 0;
  width: 160px;
  background-color: #202124;
  color: #ffffff;
  text-align: center;
  border-radius: 6px;
  padding: 6px 10px;
  position: absolute;
  bottom: 150%; /\* Adjusted to accommodate arrow \*/
  left: 50%;
  transform: translateX(-50%);
  transition: opacity 0.2s ease-in-out;
  font-size: 11px;
  line-height: 1.4;
  z-index: 99;
  font-weight: normal;
  white-space: normal;
  box-shadow: 0px 4px 8px rgba(0,0,0,0.25);
}

/\* Creates the visual pointer/arrow under the speech bubble box \*/
.tooltip-text::after {
  content: "";
  position: absolute;
  top: 100%; /\* Sits precisely at the bottom boundary of the text box \*/
  left: 50%;
  transform: translateX(-50%);
  border-width: 5px;
  border-style: solid;
  border-color: #202124 transparent transparent transparent; /\* Match background color \*/
}

.tooltip-container:hover .tooltip-text {
  visibility: visible;
  opacity: 1;
}
\`}

|   |   |   |   |   |   |   |
| - | - | - | - | - | - | - |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |
|   |   |   |   |   |   |   |

### Additional Notes

- Owner, Super Admin, and Workspace Admin have broad access across most features and can perform high-level administrative actions.
- These roles can also unmask and view details within User Profiles.
- To unmask the details, navigate to the required profile after logging in with the respective role and click the eye icon available on the profile.
- Each workspace can have only one Owner.
- Only the Owner can add Super Admins, and any Super Admin added by the Owner will automatically be added to all workspaces under that Owner.
- Certain permissions may vary by feature (for example, test-only access, view-only access, or restricted actions like Go Live / Fire), as detailed in the table above.

### Add-On Policies

Add-on policies provide fine-grained control over specific actions.
![](/images/add-on-policies.png)

They are useful when a user needs limited administrative capabilities without being assigned a higher role.

### Invite Team Members and Modify Roles

This policy allows a user to:

- Invite new team members
- Remove users
- Modify roles
- Assign or update add-on policies

This is typically assigned to IT or operations teams responsible for onboarding and access management.

### Inviting and Viewing Team Members

To create a new team member, follow the below steps:
![](/images/invite-team-member.png)

1. From your Fyno account, click on the Workspace Settings icon from the bottom left side of the navigation menu.
2. Navigate to the Team tab.
3. Click `+ Invite Team Member`.
4. Enter the user’s Email ID.
5. Select a Role based on the level of access required.
6. Optionally attach Add-On Policy to the user.
7. Click `Send Invite`.

The newly invited colleague will receive an email with details to sign up on the Fyno application.

You can invite new members to collaborate within your workspace by following these steps.

### Role Assignment Rules

- Owner can assign any role.
- Super Admin can assign Workspace Admin, Developer, Campaign Manager, Support, or Default roles.
- Workspace Admin can assign Developer, Campaign Manager, Support, or Default roles.
- Add-on policies can be assigned during invitation or updated later.

### Modifying Roles and Add-on Policies

You can update a user’s role and policies after they have been added.
![](/images/modify-role.png)

> Note: These updates are permission- and role-specific, ensuring changes only affect the selected user’s access and do not impact other users or settings.

**Steps**:

1. Navigate to Team from **Workspace Settings**.
2. Locate the user in the list.
3. Click the **three-dot** menu next to the user.
4. Select **Modify**.
5. Update the role and/or add-on policies.
6. Save the changes.

All role and permission updates are managed through the three-dot menu to ensure controlled access and avoid unintended changes.

### Deleting a Team Member

To delete a team member from your workspace, follow the below steps:

1. From your Fyno account, click on the Workspace Settings icon from the bottom left side of the navigation menu.
2. Select **Team**.
3. Click the **three-dot** menu next to the user.
4. Select **Delete**.
5. Confirm the action.

> Note: This action is role- and permission-controlled. Only users with the appropriate permissions can delete team members, and this action is permanent.

### Approver

Users with the Approver policy can:

- Access the Approval Requests page
- View all requests assigned to them across modules
- Review and take action (approve/reject) on those requests

They do not have direct access to modules, unless explicitly granted through another role.

### Approval Settings

![](/images/team-approval-settings.png)

To enable Approval settings:

1. From your Fyno account, click on **Workspace Settings** and navigate to the **Team** tab.
2. Click **Approval Settings**.
3. On the left-hand side, you will see a list of team members who have been assigned the Approver policy. At least one approver must be present to enable approval requests.
4. On the right-hand side, enable approval requests for the required modules, such as:
   - Templates
   - Notification Events
   - Workflows
   - Routes
   - Campaigns

Once enabled, any changes made in the selected module will go live only after the assigned approver(s) approve the changes.

5. Select the number of approvals required for each module. You can select up to 5 approvers.

For example, if 2 approvers are selected for Templates, any changes made to Templates will go live only after both approvers approve the changes.

6. Click **Save**.

You can read more about it [here](https://www.fyno.io/docs/approval-request)

### Important Pointers for your Reference

- Roles define baseline access, while add-on permissions provide additional capabilities.
- Certain actions, such as inviting users or modifying roles, require explicit permissions.
- Features may be disabled or hidden if access is not granted.