TURNOVERAPPLICATION SYSTEMS
ContactStart Free
Security and control

Access and permissions stay intentional.

Turnover uses authenticated access, program authorization, and assigned permissions. Security and deployment details should be reviewed for the customer’s specific configuration.

Discuss SecurityCustomer Login
HTTPS connections when properly deployedApproved user accountsLocal Admin and limited contributor access
Illustrative interface, example data
ACCESS CONTROL
Authenticated accountUser signs in through approved access
REQUIRED
Program authorizationEmail and domain controls where configured
CONTROLLED
External contributorLimited workspace, no normal module access
LIMITED
Practical controls

Protect the program without blocking the work.

Turnover combines authenticated access with program-level authorization and role-specific workflows.

AUTH

Authenticated access

A user signs in through an approved account before entering an authorized program.

PROGRAM

Email and domain controls

Approved emails and domain controls can limit who is allowed into a specific program where configured.

ADMIN

Local Admin responsibilities

Designated Local Admins manage supported access, permissions, alert subscriptions, and reviewer workflows.

Limited workspaces

Give contributors only the access they need.

Approved third-party contributors can be routed to a limited workspace for configured submissions. They do not receive normal access to the internal Turnover modules or protected customer program data.

  • Submit configured work details, dates, labor context, pictures, and closeout information
  • Internal reviewers can approve, request clarification, or sign off
  • Reviewer authorization remains separate from normal contributor access
  • Program modules can be enabled or hidden based on configuration and permissions

Access paths

Internal authorized userAssigned program and module access
APPROVED
Local AdminSupported access and permission management
CONTROL
External contributorLimited submission workspace only
LIMITED
Shared responsibility

Security also depends on customer choices.

Customers should use unique accounts, protect credentials, remove access when roles change, review Local Admin assignments, and avoid entering data that is not appropriate for the configured program.

Turnover should not be described as providing absolute security. No internet-connected software can guarantee that. Specific hosting, authentication, storage, backup, retention, and compliance requirements should be reviewed before deployment.
Put experience to work

Review the security model for your configuration.

Discuss account authorization, domain controls, permissions, contributor access, and deployment requirements before launch.

Contact TurnoverTalk With Turnover
Two ways to start

Start on your own, or start with us.

Turnover does not require a sales conversation before you can learn whether it fits. The guided path remains available for teams that want a demonstration, commissioning help, or a planned rollout.

Self-enrollment

Try Turnover without talking to anyone.

Create a free authenticated account, verify the account, create your own program, build the required site or facility structure, and begin using real work to evaluate it.

  1. Create and authenticate the free account
  2. Create the Turnover program
  3. Build the required structure
  4. Invite appropriate authorized teammates and begin
Create Free AccountSee the Self-Trial Steps
Guided sales and setup

Bring Turnover into the conversation.

Schedule a call, review a specific workflow, or ask Turnover to help with commissioning, structure, permissions, module selection, and rollout planning.

  1. Schedule a focused call
  2. Review the real workflow and participants
  3. Request optional commissioning assistance
  4. Plan a broader rollout when it earns one
Schedule a CallAsk About Commissioning