User Location Assignments

Assign users to branch or operating locations so access, ownership, and reporting match the agency structure.

User Location Assignments connect users to the locations where they work. Use this page when your agency has branches, country offices, remote teams, or operating groups that should affect access, ownership, and manager review.

A user can belong to one or more locations. The right setup helps Edmissa show the right student profiles, applications, Leads, tasks, and reports to each person.

What this guide helps you configure

Area	What it helps with
User assignment	Assign a user to the branch or team where they work.
Bulk changes	Update several users when a branch or team structure changes.
Access review	Confirm users can see the work they should see.
Reporting	Keep branch and team reporting cleaner.

Before you start

Prepare these items before assigning users:

Item	Why it matters
Active locations	Locations should exist before users are assigned to them.
Role plan	Location assignment works with role scope. It does not replace roles.
Default location	Users with multiple locations should have a clear primary location.
Manager review	Managers should know which users belong to their branch or team.
Test user	Use one sample user before making large assignment changes.

Review Locations, Users, and Permissions and scope before assigning many people.

Open User Location Assignments

Use this path when you want to assign users to locations:

Open Settings.
Open User Locations.
Confirm the page title is User Location Assignments.

The direct route is /t/settings/user-locations.

The page includes these actions:

Action	What it does
Bulk Assign	Assign or update location access for several users.
Assign User	Assign location access for one user.
Filter by location	Review users connected to a selected location.
Filter by access	Review users by assignment or access state when available.

Assign one user

Use Assign User when you need to update one person's location access.

Open User Location Assignments.
Select Assign User.
Choose the user.
Choose the location or locations shown in your workspace.
Confirm the user's primary or default location when the page asks for it.
Save the assignment.
Test the user's access if the change affects live work.

For a counselor in one branch, assign the branch where they work. For a manager who reviews several branches, assign the locations they are responsible for and confirm the role scope supports manager visibility.

Use Bulk Assign carefully

Use Bulk Assign when several users need the same location update.

Bulk changes are useful when:

A new branch opens.
Users move from one office to another.
A remote team is created.
Managers need access to a group of locations.
A test setup needs to be cleaned before launch.

Before using Bulk Assign, confirm the location name, the users included in the change, and the expected access result. A bulk assignment can affect many daily views, so test with a small group first when possible.

Recommended first version

For a study abroad agency, start with a simple pattern:

Role type	Suggested assignment
Counselor or consultant	Assign to the branch or team that owns their daily student work.
Application officer	Assign to the processing team or office responsible for application work.
Branch manager	Assign to the branch or branches they manage.
Central admin	Assign to the locations they must support across the workspace.
Temporary user	Assign only the location needed for the temporary work.

Avoid giving every user every location unless they truly need it. Broad access can make lists, reports, and accountability harder to understand.

How location assignments affect access

Location assignment works with roles and scope.

Setup piece	What it controls
Role	What the user can do.
Scope	Which work the role applies to.
Location assignment	Which branch or operating location the user belongs to.

If a user cannot see expected work, check all three pieces. A user may have the right role but the wrong location assignment, or the right location but a role with too narrow a scope.

Test after setup

After assigning locations:

Open the user's profile in User Management.
Confirm the assigned locations are correct.
Confirm the default location is correct when the user has more than one.
Sign in as a test user with the same role and location pattern.
Confirm the expected student profiles, applications, Leads, and tasks are visible.
Confirm work from other locations is hidden when it should be hidden.
Ask a manager to review a location-filtered list or report.

Guide	Use it for
Locations	Create and maintain branch or operating locations.
Users	Invite users and review account status, roles, and sessions.
Roles	Build reusable access profiles.
Permissions and scope	Understand how roles, scope, and locations combine.
Access and permissions troubleshooting	Diagnose missing pages, disabled actions, or unexpected visibility.

User Location Assignments

On this page