Team Settings: managing team and user permissions
Last updated: July 27, 2026
Team Settings (Settings → Team): add members via + New Team Member (name, email, role); edit/delete via hover icons — deletion cannot be undone. On Edit Team Member, pick a Role then override individual Permissions (scopes: All/Assigned/Yes/No) across the Direct Sales and School permission groups. Permissions are opt-in, and adding members may be limited by the user slots in your plan.
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 quote 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.