👪Onboarding a CS Team
Last updated
Last updated
Forest Admin is a powerful admin panel solution that offers advanced roles and permissions management, making it ideal for growing companies that need to onboard new teams, such as Customer Support. In this tutorial, we will guide you through the process of onboarding a Customer Support team on Forest Admin using roles, permissions, team-based layouts and scopes.
Forest Admin has four default levels of administrative permissions: Admin, Developer, Editor, and User. It is a security layer that determines who can access the Project Settings and edit the UI layout. User access can be further customized with Roles.
Only Admins can manage permission levels from the Project Settings.
Read more about user permissions in the documentation.
Create Custom Roles: Roles in Forest Admin allow you to restrict access to specific data and define what actions users can perform. For your Customer Support team, you can create roles that align with different support levels or responsibilities.
Example Role Setup: For instance, set up roles like "Level 1 Support," "Level 2 Support," and "Level 3 Support." Each role can have different permissions based on the tasks they need to perform.
Assign Users and Permissions: When creating a role, assign team members to it and specify their permissions. For example, a Level 1 Support role may have read-only access, while Level 2 and 3 roles can edit data and trigger actions.
Configure Smart Actions: Customize which actions are available to users with each role. This allows you to create a complex workflow tailored to your Customer Support team's needs.
Read more about Roles in the documentation.
Understanding Scopes: Scopes are dynamic filters that control what data is visible to users. In your scenario, you can set up scopes to filter data based on user locations or other criteria.
Example Use Case: If your company has offices in multiple locations, configure scopes to show French Customer Support members data related to France and German Customer Support members data related to Germany.
Easy Configuration: Setting up scopes is as straightforward as teams and roles. Remember that scopes are linked to collections and are configured in the Layout Editor Mode within Collection settings.
Read more about Scopes in the documentation.
Power of Team-Based Layouts: Teams allow you to create different layouts for different groups within your organization. This can greatly enhance the usability of Forest Admin for your Customer Support team.
Customizing Layouts: For instance, you can tailor layouts to display essential information first. For Customer Support, you might prioritize showing the transaction ID or specific customer data.
Create and Configure Teams: To set up teams, go to Project Settings, select Teams, and create a new team. Give it a name, add users, and either copy a layout configuration from a similar team or create one from scratch.
Identify New Team Members: As your Customer Support team grows or changes, you'll need to invite new team members to use Forest Admin. Identify the individuals who need access to the system based on their roles and responsibilities.
Access User Management: Go to the Users section of the Project Settings. Provide email addresses of team mates you want to invite to Forest Admin.
Assign Roles and Teams: Assign them to the appropriate Roles and Teams, and set their Permission Level. Confirm that each team member's permission level align with their roles. Double-check that they have the necessary access to perform their tasks effectively. You can also assign them a relevant tag or tags.
Send Invitations, and provide Training and Support: As new team members join, offer training and support to help them get acquainted with Forest Admin's interface and features. Ensure they understand their roles and responsibilities within the system.
Monitor Access: Regularly review and monitor access to Forest Admin to ensure that team members have the appropriate permissions. Adjust roles and permissions as needed based on changes in team dynamics.
