Inviting and managing users

Invite people to the correct Perslace workspace and give each person only the access needed for their work.

For: Admin and Primary Admin

Prerequisites

Authority to invite users
Approved recipient email addresses and job titles
A confirmed role for each recipient
Approved synthetic or test users when documenting the workflow

Invite a user

Open Employees > All Employees, then open the invitation form.
Choose an invitation method: Manual, Google, Microsoft 365, or Slack.

Only the availability of these methods was verified. Connected-account flows still require safe testing.
For a manual invitation, enter the person’s email address and job title.
Choose Employee, Manager, or Admin.

Admin includes full workspace settings and billing access. Confirm the recipient and role before sending the invitation.
To invite more people, select Add another recipient and check every row independently.
Send invitations only to approved synthetic or test recipients while documenting the workflow.

The form states that recipients have seven days to accept. Delivery and acceptance were not exercised during the product review.
Return to All Employees and review the available membership information.

Pending, accepted, and expired invitation states still need controlled verification.
Review each existing user’s employee ID, group, scheme, manager, branch, role, and status where available.

Role changes, deactivation, removal, invitation resend, and Primary Admin transfer also require controlled verification before they are documented as supported procedures.

Expected result

After controlled verification, the recipient should receive a seven-day invitation for the selected workspace and role. How Perslace displays each membership state remains unverified.

Important notes

Invite only approved users to the test organisation while validating the workflow.
Do not include user lists, personal email addresses, or employee identifiers in screenshots or support requests.
User lifecycle actions may affect access and historical ownership. Check dependencies before making a change.
Use the least-privileged role that supports the person’s responsibilities.

Troubleshooting

The invitation did not arrive

Confirm the address, then ask the recipient to check spam and email quarantine. Ask them to use only the newest invitation.

The invitation expired

Issue a new invitation only after the exact resend or reinvitation process has been verified in the test organisation.

The wrong role was selected

Do not assume that editing the role after sending is safe. Ask the Primary Admin to review the account before the recipient continues.

A directory import fails

Record the provider, time, and sanitised error message. Do not include tenant identifiers, account details, tokens, or credentials.

Last updated: August 2026