Skip to main content
Audience: MSP staff with Company-user settings access. Open Settings > Users & Roles > Company Users, or the client-user step in Launch Center.

​
Prepare the pilot users

  1. Review existing users before importing again. Confirm their company, email, active state and access group.
  2. For provider records, follow the integration’s user-import workflow and confirm company mappings first. A synchronized contact in staging is not necessarily a portal user.
  3. Assign the intended Company access group. Review provider contact-type rules, company defaults and integration defaults where synchronization manages roles.
  4. Verify the saved user record and intended access. Keep invitations and other communications as separate deliberate actions.
  5. Repeat for each company in the rollout, then review Launch Center’s client-user finding.
Use the detailed Users & Roles settings and user import guide for supported actions. Do not assume every provider offers the same Import from M365 or Import from PSA button in the user table.
Filter Company users by name, email and account type before reviewing individual records.

Filter Company users by name, email and account type before reviewing individual records.

​
What counts as ready

The launch check requires an active Company user with a company assignment and an access role for every rollout company. A staged contact, inactive record or unassigned user does not satisfy it. A passing check still does not prove that the person can complete every intended task or has received an invitation. Access Groups control permissions. Team Roles assign responsibilities and account teams. Assigning a team responsibility does not replace the user’s access group.

​
Troubleshooting

If a user’s role changes after synchronization, inspect explicit contact-type rules before overriding it again. If the user belongs to the wrong company, correct the source mapping and assess the affected records before importing more. If the user cannot sign in, inspect identity and access status separately from the integration connection.

​
FAQs

No. The check needs an active portal Company user with company and access-role assignments.
No. Every rollout company needs its own qualifying user evidence.
No. Verify user creation and access separately from invitations and communications.