Assign staff to customers
Invite staff into bounded partner roles, assign customers, and explain what each person and each customer can see.
TenantVigil only reads your Microsoft 365 tenant. It never changes a setting: you apply each fix yourself.
Need a hands-on starting point?
Start with one tenant or talk to the team if you want help evaluating fit, permissions, or rollout approach.
Admin and member visibility
Partner admins see every customer the MSP owns. Members see only the customers assigned to them.
Each person's console access follows their current grants. If a grant ends, a suspension lands or the customer moves to another MSP, the person's view of that customer ends.
Invite staff
Invite staff into bounded partner roles from the Team page. An invitation does not grant Microsoft administrator privileges in any customer tenant.
An invite stops working if its issuer loses approval or invitations are disabled.
Assign customers
A partner admin assigns a member to the customers they support. The member can then move between those customer contexts from My customers.
Console access is not Microsoft consent. A staff member who can open a customer in TenantVigil still needs that customer's administrator consent before TenantVigil reads the tenant, and any native change still needs its own Microsoft setup.
What the customer sees
A customer's owners and admins see the MSP people who can open the organisation now, their role and grant date, what the MSP did there in the last 90 days that TenantVigil records, and what is not recorded.
The customer's view is a plain-English explanation of access, not a substitute for the customer's own Microsoft permission review.
Next action
Review the permission model before the first native change, or start with the daily scans and findings guide.
- Microsoft permissions and customer access
- Scans, findings and freshness