Managing your team: members, roles, and permissions
Last updated: October 23, 2026
Manage your team from Settings → Team: invite members (name + email), edit, and remove them (removal is irreversible). Assign roles (saved permission configurations, including the built-in Admin role) and override individual permissions per member using All/Assigned/Yes/No scopes across the Direct Sales and School permission groups; some permissions are school-specific.
School accounts on Edvisor support unlimited team members.
Managing team members
How to access
Settings > Team (third tab).
Add (invite) a team member
- Enter first name, last name, and email address.
- Click Invite team member.
- The person receives an email invitation. They follow the link to complete their account.
Remove a team member
- Locate the user in the team settings page.
- Hover over their user card.
- Click the delete icon when it appears.
- Confirm in the popup.
Important. This action cannot be reversed.
Permissions
School accounts support role-based permissions. By default, team members have full access, but you can assign roles (saved permission configurations) and adjust individual permissions for each member from Settings → Team. Some permissions are school-specific — such as Enrollments, School Connections, Agency Portal, Inventory (Packages and Promotions), Offerings (Publish Courses), and School Insights.
For setup steps, see the Managing team and user permissions and Custom roles sections below.
Managing team and user permissions
Manage your team, their roles, and their permissions.
How to access
User icon (top right) → Settings → Team.
Before you start
- You need permission to invite and manage team members.
- Adding members may depend on the number of user slots in your plan.
Add new team members
- Click + New Team Member.
- Fill in: name, email, and role.
- Click Save.
The new member receives an email invitation. They must accept it to access Edvisor.
To resend the invitation: hover over the team member's name and click the Resend invitation email icon.
If you cannot add a member, you may have used all the user slots in your plan — check your plan before inviting more people.
Edit a team member
Hover over the team member's name and click the pencil icon to edit their personal details, role, or permissions.
Set permissions for a team member
On the Edit Team Member screen, choose a Role to set the member's baseline access, then adjust anything individually under Permissions to give that person custom access.
Permissions are grouped by area. Agency-side areas sit under Direct Sales (Students, Bookings, Proposals, Invoices, Sales, Schools, Reporting, Payments, Settings, Agency Connections, Inventory, and inviting users). School-side areas sit under School permissions (Agency Portal, Enrollments, School Connections, Inventory, Offerings, School Insights).
Each permission is set with a scope:
- All — applies to all records in that area.
- Assigned — applies only to records assigned to this member.
- Yes — allowed (for permissions that aren't record-based).
- No — not allowed.
Some permissions are nested under a parent (for example, Create and Edit Students sits under View Students), and a few are inherited from another area (shown as "set in …").
What you can do with this:
- See offerings without editing them — allow View Accommodations but set Create and Edit Accommodations to No (useful for selecting accommodation on a proposal without full inventory access).
- Show someone only one side of applications — grant Bookings (agency) without Enrollments (school), or the reverse.
- Control who can manage connections — the Agency Connections and School Connections permissions.
- Control who can add team members — the Invite Team Members permission under User.
Permissions are opt-in: until you change them, members keep their existing access, so there is nothing to set up unless you want to restrict someone.
Delete a team member
Hover over the team member's name and click the bin icon. Alternatively, click the pencil icon and select Delete. Confirm in the popup.
Important. Removing a team member cannot be undone.
Best practices
- Delete users as soon as they leave to maintain account security.
- Use roles for common access patterns, and per-member overrides for exceptions.
- Update roles and permissions promptly when responsibilities change.
Custom roles
Roles are saved permission configurations you can assign to team members, so you don't have to set every permission individually for each person.
How to access
Settings → Team, then scroll down to the Roles list.
Before you start
- You need permission to manage team settings.
- Every account has a built-in Admin role. It grants full access and cannot be changed.
Built-in Admin role
Every account has an Admin role ("Access Everything"). It grants full access and cannot be modified. Assign it carefully.
Create a role
- In the Roles list, click + New Role.
- Enter a Role name.
- Set the permissions for the role (see below).
- Click Save.
Setting permissions
The role editor uses the same permission options as an individual team member. Permissions are grouped by area — agency-side under Direct Sales (Students, Bookings, Proposals, Invoices, Sales, Schools, Reporting, Payments, Settings, Agency Connections, Inventory, inviting users) and school-side under School permissions (Agency Portal, Enrollments, School Connections, Inventory, Offerings, School Insights).
Each permission is set with a scope:
- All — all records in that area.
- Assigned — only records assigned to the member.
- Yes — allowed (for permissions that aren't record-based).
- No — not allowed.
Assign a role
- Assign it when you add a new team member.
- Reassign anytime: hover over the team member, click the pencil icon, and change the Role.
After you assign a role, you can still override individual permissions for that one person on their Edit Team Member screen.
Edit or delete a custom role
Hover over the role in the Roles list and use the pencil icon to edit it or the bin icon to delete it. The Admin role cannot be changed.
Why roles help
Different team members need different access — for example, counselors with full student access but no admin settings, finance staff with payments and reports, or junior staff with limited create and edit. A role captures one of these patterns once, so you can apply it to many users instead of configuring each person by hand.
Use roles for common access patterns, and per-person overrides for the exceptions.