Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.arcuserp.com/llms.txt

Use this file to discover all available pages before exploring further.

This guide is for internal Arcus app users. Customer portal users sign in through the separate customer portal flow and do not use internal roles, entity access, or admin-managed MFA reset.

​
Accept An Invitation

Admins invite internal users from Organization Users. The invitation decides the email address, starting role, entity access, and optional location restrictions.
Organization Users page with user list, entity memberships, role chips, status, actions, search, and pending invitations
  1. Open the invitation email.
  2. Follow the invite link.
  3. Confirm the email address shown on the page.
  4. Create or confirm your password.
  5. Sign in to Arcus.
  6. Complete any required MFA setup before starting work.
If the invitation expired, ask an admin to resend or revoke and reissue the invite. Do not ask the admin to change your display name around a typo. The email address itself should be corrected with a new invite.

​
First Sign-In Checklist

After the first successful sign-in:
  • Confirm the correct entity opens.
  • Open the user menu and review Profile.
  • Set up required MFA.
  • Save recovery codes when prompted.
  • Confirm the sidebar shows the modules you need for your job.
  • Ask an admin to review role, entity membership, or location access if anything is missing.

​
Complete MFA Setup

Arcus can require MFA before users can continue into the app. MFA setup may include an authenticator app, a security key, or email-code MFA depending on the user’s policy and available factors.
Profile page with account information, identity verification, password, PIN lock, authenticator app, security key, and email-code MFA controls
Recommended setup:
  1. Enroll an authenticator app or security key.
  2. Save recovery codes in a secure place outside Arcus.
  3. Add a backup factor when your company policy allows it.
  4. Avoid relying only on email-code MFA when a stronger factor is available.
  5. Confirm you can sign out and sign back in.
Recovery codes are emergency credentials. Do not paste them into tickets, chat, email, shared notes, screenshots, or documentation.

​
If MFA Enrollment Blocks You

When Arcus requires MFA, you may be redirected to the setup page until a valid factor is enrolled and required recovery-code acknowledgment is complete. Use this checklist:
  • Finish enrollment for at least one factor.
  • Confirm any email-code challenge from the same browser session.
  • Save recovery codes if the page asks for confirmation.
  • Refresh after enrollment if the sidebar still does not appear.
  • Contact an owner or admin if enrollment fails or your old factor is unavailable.

​
Recover With A Recovery Code

Use a recovery code when you know your password but lost access to an enrolled factor. Recovery-code sign-in consumes one saved code and clears existing MFA factors so you can enroll again. After using a recovery code:
  1. Sign in again.
  2. Complete the forced MFA setup.
  3. Save the new recovery codes.
  4. Tell an admin if you suspect the lost factor or old codes were exposed.

​
Admin Reset MFA

Admins can reset another user’s MFA from Organization Users after verifying the person through the company’s internal process. The reset:
  • Clears the user’s enrolled MFA factors and recovery codes.
  • Records the reason for audit review.
  • Requires the user to enroll a new factor at next sign-in.
  • Does not change the user’s password, role, or entity access by itself.

​
Common Blocks

  • Invite missing: ask the admin to verify the exact email, pending invite state, and email log.
  • Invite expired: resend the invite or revoke and create a corrected one.
  • Wrong entity opens: ask an admin to review entity membership and default entity access.
  • Module missing: check role, custom permissions, module settings, and location access.
  • Recovery code already used: each recovery code can be used once.
  • Admin reset was completed but user still blocked: the user must sign in and enroll a new MFA factor.
  • Only owner is locked out: use the company’s break-glass recovery process because no other owner can reset access from the UI.

User Management

Invite users, manage entity access, resend invitations, revoke invitations, and reset MFA.

Roles and Permissions

Create custom roles, assign least-privilege access, and review effective permissions.

Profile and Security

Manage your own profile, PIN, MFA factors, security keys, and recovery options.

Navigation Overview

Find modules, records, settings, and support tools quickly after sign-in.