Accounts, roles and the client portal
Video guide: Inspect account roles before testing portal access
Recorded October 22, 2026 in the fictional Summit Managed IT staging workspace, App 0.432.1. The deployed demo can differ from the current product; use the written guide for current behavior. No invitation, permission change, real end-user login or cross-customer access test.
Full narration captions are included in the video. Open video full screen · Download subtitles · Download transcript
Video transcript
Open Administration, Accounts, End Users. Confirm the intended customer before creating or changing access. This fictional workspace contains demonstration accounts. We do not invite a person, send email or change permissions in this recording.
Open End User Roles to inspect portal tabs and access choices. Domain admin, User and Guest permissions are different; staff use Technician Roles. Remote-access permission and explicit device grants must be tested for the intended role; a role name alone is insufficient.
Follow the guide to create the minimum required access. Verify the actual portal as that user and test denied customer and device access as well as allowed access. Do not use a client administrator grant list as though it restricts their whole-customer access.
Technician accounts
Staff roles include OWNER, ADMIN, MANAGER and TECH. Owner/admin roles manage configuration; the Technician Roles matrix controls supported permissions, while some operations remain restricted to Owner/Admin regardless of that matrix. Administration > Accounts > Technician Users adds people, sends account setup mail with a temporary password, forces a password change on first sign-in, and requires the deployed two-factor setup before workspace use. Supported sign-in methods include authenticator codes and passkeys; retain recovery codes privately. Technician Roles is the permission matrix per role; Technician Groups organize people for alert routing, escalation and ticket assignment, with a manager per group and the organizations each group covers.
Sign-in security (Security > Sign-in Security)
Login lockouts after repeated failures, automatic IP blocks for scanners and endpoint probing, a permanent block list, and an allow list (exact IP or CIDR) that beats every block: add only trusted, deliberately selected addresses; a broad allow list can bypass protections you intended to retain. Locked accounts can be unlocked and blocks lifted from the page; every action is audited. Authenticated 404s are exempt from scan detection. Each lockout, block and scan opens an alert (source Sign-in security) whose case, notification and ticket behavior is set on Alert Rules > Sign-in security.
Password resets
Forgot password on the sign-in page emails a single-use link through the workspace mailbox, falling back to the platform relay. Administrators can issue a reset from the user's row.
Client portal
What customers get, on the same workspace host, after signing in with a client role: Dashboard, Tickets (new ticket with forms and drag-and-drop attachments, replies), Devices (their managed computers with status, Take Control for granted devices, network devices dashboards, mobile devices), Assets, Patching, Antivirus, Identity (ITDR connection and sign-in feed), Reports, Activity (the customer activity report), Compliance, Passwords (a private per-user vault with encrypted secrets and CSV or password-protected ZIP export), Microsoft 365 (read-only posture), Training, Email Security, Documentation (client administrators only), Billing (client administrators only), Cases.
The support navigation entry is Cases when that tab is enabled, otherwise Tickets when Tickets is enabled; the navigation does not show both entries together. Which configurable tabs each client role sees is one workspace-wide matrix at Administration > Accounts > End User Roles (role by tab). Documentation and Billing remain client-administrator-only and sit outside that matrix. Older per-organization overrides made from the retired portal Settings page are listed there with a Reset. The portal navigation and tab URL guards follow the effective visibility settings; object-level permissions and device-control grants still apply. Dark mode is the default for the portal and the app; the header toggle switches it.
Steps
- Technician: Administration > Accounts > Technician Users > Add: name, email, role. The person receives the setup email, sets a password and completes the required two-factor setup.
- Roles and groups: adjust the matrix on Technician Roles; create groups and assign organizations on Technician Groups.
- End users: Organizations, locations and customer users. Portal tab visibility: End User Roles.
- Sign-in security: review locks and blocks, and add a narrowly scoped trusted address only when required.
Access reviews
Administration > Accounts > Access Reviews lists staff or one customer's end users. Review the listed access and record whether to keep or flag each account. A flag records a review decision; disable an account explicitly when access must stop. Device assignment alone does not grant remote control. When Allow remote control is enabled, CLIENT_ADMIN can control all devices in their customer organization; individual grants constrain CLIENT_USER and CLIENT_GUEST, not CLIENT_ADMIN.
Verification
- A new technician cannot reach any page until two-factor authentication is enrolled.
- Unticking a tab for CLIENT_USER hides it in a test user's portal and returns them to the dashboard on a direct URL.
Troubleshooting
- Locked out: Security > Sign-in Security > Unlock, or clear the IP block; the allow list prevents recurrence.
- A customer sees tabs they should not: a stale per-organization override; Reset it on End User Roles.
