Account Access
User accounts, sign-in controls, and role assignments help limit access to the people who need it.
Security starts with the right access
ClearView combines account controls, organization separation, and practical operating rules so teams can work without opening every record to every user.
Organization Separation
Company records are organized by customer organization so one tenant does not operate inside another tenant’s workspace.
Role-Based Visibility
Office, field, management, and administrative responsibilities can be separated according to business needs.
Secure Connections
Production web access uses encrypted HTTPS connections between supported browsers and the ClearView service.
Controlled Files
Operational uploads can be organized within company-specific storage paths and restricted by account access.
Activity History
Important administrative and workflow actions can be recorded to support review, accountability, and follow-up.
Protection works best when everyone participates
ClearView provides the platform controls. Each customer also plays an important role in protecting its accounts, devices, users, and business information.
ADMS Responsibilities
- Maintain the ClearView service and approved production environments.
- Use access controls and organization separation in supported workflows.
- Protect service credentials and limit administrative access.
- Maintain backup and recovery procedures appropriate to the service.
Customer Responsibilities
- Use strong, unique passwords and protect sign-in access.
- Remove access promptly when a worker leaves or changes roles.
- Keep devices, browsers, and local networks reasonably secure.
- Share only the information needed for the work being performed.
Prepared for dependable operations
Security also means protecting the ability to keep working and recover when something goes wrong.
- 01Backups and recovery checkpoints support restoration when a service issue affects stored information.
- 02Feature changes should be introduced through controlled updates rather than unreviewed production edits.
- 03Public forms and customer-facing services should use validation and rate controls appropriate to their risk.
- 04Security questions can be reviewed during onboarding based on the customer’s plan and operating requirements.
NEXT //SECURITY QUESTIONS
Need a closer review before launch?
Contact ADMS with your access, security, or deployment questions so the right requirements can be reviewed before onboarding.