Administer an invited team

What administrator access permits

Administrators can create and edit users, set initial or replacement passwords, assign administrator access, enable or disable accounts, and inspect users’ files and reports. The role grants broad data access, so reserve it for people who need that responsibility.

Administrators must enroll an authenticator. The portal refuses actions that disable or demote the signed-in administrator’s own account.

Create an account

1. Sign in to the portal as an administrator.
2. Find Invited users and the Invite a user form.
3. Enter a unique lowercase username, display name and initial password of at least 14 characters.
4. Choose whether the user needs administrator access and leave the account enabled if it is ready for use.
5. Select Create account, then deliver the initial credentials directly through an appropriate private channel.

New users change the initial password on first sign-in. New administrators also enroll an authenticator. Account creation provisions the private workspace and worker; do not create duplicate users if a request reports an error before checking the current account list.

Edit or disable a user

Select a user’s edit action to update their display name, role or enabled state. Set a replacement password when recovery is needed. Security-related changes revoke sessions; users may need to reconnect their MCP clients.

Disabling prevents access and keeps files available for administrator review. The workspace continues to use its storage allocation until the administrator arranges cleanup.

Review files and reports

Use the Review workspace selector to choose the intended user. Confirm the administrator-review notice before browsing. The library and result requests operate in that selected workspace and record the administrator and target.

Choose a saved report to open its reader or download the original files. If a record is quarantined, arrange an integrity review before using it. Return to your own workspace when finished.

When an operational issue needs attention

Record the time, username, action, and any non-sensitive error or run identifier. Check whether the account or file already exists before retrying. Do not request passwords or bearer tokens in an incident report.

Server recovery, capacity changes, backups and historical-record reconciliation are operator tasks. They are separate from the normal user-management form.