User Roles and Permissions

Overview

Roles and permissions control what each user can see and do in OneSuite. This protects sensitive areas, keeps staff focused, and prevents users from accidentally changing records outside their responsibility.

Business Value and Typical Use Cases

Give sales users CRM access.
Allow billing staff to create invoices.
Limit POS actions to cashiers and managers.
Give administrators access to settings and licensing.

Before You Begin

Confirm you can log in to OneSuite and access the module described in this article.
Make sure your organization has completed any required setup, such as license activation, user permissions, payment settings, or connected email accounts.
Use production records or approved test records when learning a workflow so you do not accidentally change live customer information.

Prerequisites and Permissions

Active OneSuite installation or trial.
User account with the appropriate role or permission.
Current production release interface.
Stable browser session.

Concepts

Permission design should follow the work people actually perform. A cashier may need POS but not administration. A billing user may need invoices but not workforce settings. A manager may need reporting or approval authority. The goal is not to hide work from staff; it is to give each role the correct tools.

How This Feature Fits Into OneSuite

Administration is a dependency for nearly every other OneSuite module. Licensing, user access, provider connections, company identity, communication settings, and operational defaults can determine whether a workflow is available or behaves correctly.

After major configuration changes, verify the affected workflow with a non-administrator user to confirm the business experience—not only the settings screen—is correct.

Screen Orientation

Administration controls the environment other users depend on. Changes to users, roles, permissions, organization settings, providers, or diagnostics should be deliberate and documented.

Before changing a setting, identify which users and workflows depend on it. A configuration change that appears local can affect email, payments, POS, phone, calendar, marketing, or login behavior elsewhere.

Use least-privilege access: give each role enough capability to perform the job without granting unrelated administrative controls.

Open the area described in this guide and pause before editing. Identify the page heading, primary action button, search/filter controls, record list or detail panel, status indicators, and any related-record or history areas. This quick orientation prevents users from applying instructions to the wrong record or module.
When the page contains both a list and a record/detail view, use the list for discovery and the detail view for action. Search or filter first, then open the exact record and verify identifying information before making changes.

Role-Specific Guidance

Administrators are responsible for configuration accuracy, access control, provider connections, and safe change management.
Managers should request access changes based on operational need rather than sharing administrator credentials.
End users should report configuration symptoms with enough detail for an administrator to reproduce the issue instead of changing settings themselves.

Step-by-Step Instructions

Open the user or administration area available to administrators.
Review the user account that needs access.
Assign the role or permissions that match the person’s job.
Save changes.
Have the user sign out and sign back in if navigation does not update immediately.
Verify that the user can access required modules and cannot access restricted areas.

Expected Results

When completed, the record, action, or workflow described in this guide should be visible in OneSuite, searchable from the appropriate module, and connected to the related customer, company, invoice, payment, communication, or activity history where applicable.

Verification Checklist

Confirm the correct OneSuite user is signed in and the expected role/permissions are active.
Confirm the customer, company, invoice, product, message, appointment, employee, or other record shown on screen is the one intended for the task.
After saving or completing the action, refresh or return to the relevant list and verify the new status, history entry, balance, message, appointment, or record appears where expected.
Verify both organization entitlement/license state and the individual user’s role/permission state when a module or action is unexpectedly unavailable.

Business Workflow

Job responsibility → Role assigned → Workspace menu changes → User completes authorized work → Administrator reviews access when duties change.

Real-World Business Scenarios

New employee onboarding: assign the minimum role/access required, sign in as or validate with the user, and confirm the expected module navigation before live work begins.
Access change: document why access is changing, update only the required permission/role, and verify both newly available functions and functions that should remain restricted.
Feature appears missing: verify license/entitlement and user permission separately before changing either one.

Advanced Operational Guidance

For repeatable business work, standardize naming, ownership, tags/statuses, and staff responsibilities before increasing volume. Consistency makes OneSuite search, reporting, history, and handoffs substantially more useful.
When multiple modules participate in the workflow, verify each handoff. Do not assume that completing one screen automatically proves the customer, payment, communication, or reporting outcome is correct elsewhere.

Screenshots

Production screenshots appear here only after approved OneSuite captures are attached. Written instructions are complete without screenshots.

Best Practices

Use least-necessary access for everyday users.
Review permissions when employees change roles.
Document which roles your organization uses.

Common Mistakes

Making every user an administrator.
Forgetting to update access after staffing changes.
Troubleshooting missing buttons before checking permissions.

Troubleshooting

Symptom: the page or button is not visible. Cause: your role may not include access to this module or the current license may not include the feature. Solution: ask an administrator to review your role, workspace access, and license status. Verification: sign out, sign back in, and confirm the menu item appears.
Symptom: a saved record cannot be found. Cause: filters, search terms, ownership, or status views may hide records. Solution: clear filters, search by name, email, phone, invoice number, or company, and check active versus archived views. Verification: open the record and confirm the latest information appears.
Symptom: a workflow stops before completion. Cause: required fields, connected account setup, payment configuration, or missing customer details may be incomplete. Solution: review the required fields shown on the page and complete setup items before retrying. Verification: repeat the step and confirm the expected success message or updated status appears.

Frequently Asked Questions

Why can one user see more modules?: Their role may include more permissions.
Should owners be administrators?: Usually yes, but daily work can still be done from standard roles.

Next Steps

Continue with the Related Articles section to follow the workflow into the next OneSuite function instead of returning to the homepage after every task.

Last Updated: August 21, 2026
Version: 0.3.2-Phase2B-SHORTCODE-RENDER-RECOVERY
Verified Public Source Baseline: PASS35H66DN RC1 GOLD R63.97
Documentation Revision: Phase 2B Enterprise Detail Expansion