Guide 01

Start a company workspace

  1. Choose the plan and billing interval on the live pricing page.
  2. Create the Workspace Owner account through the secure signup flow.
  3. Confirm the company workspace details used for provisioning.
  4. Invite only the people who need access and assign a base role.
  5. Add permission packs and scope only where the person’s work requires them.
  6. Validate the main workflow with demo or approved test records before wider rollout.

Plan entitlement and user authorization are separate checks. A plan can include a capability without granting every user access to it.

Guide 02

Assign roles without creating role overload

  1. Give each user one understandable base role.
  2. Add business permission packs such as HR, Finance, Payroll, Projects, Sales or Support.
  3. Set scope so access applies only to the appropriate records or area.
  4. Use reusable access templates for common assignments.
  5. Review exceptions and sensitive access through the available audit trail.

Read the security and access model →

Guide 03

Move a payroll period from setup to payslip

  1. Confirm the employee, country, legal entity, salary structure and pay period.
  2. Review attendance, leave and overtime inputs for the period.
  3. Calculate the run using supported native rules, configured employer rules or approved provider inputs.
  4. Review, prepare and verify the run with the responsible payroll role.
  5. Approve and finalize the period through permissioned actions.
  6. Publish the employee’s own payslip and retain the period history.

See country and legal-entity boundaries →

Guide 04

Resolve a support issue with clear ownership

  1. Create or receive the ticket with the requester’s context.
  2. Assign one owner and move the ticket into progress.
  3. Keep public replies and internal notes attached to the same issue.
  4. Mark the issue resolved only after the work is completed.
  5. Confirm closure and reopen the same trail if the issue returns.

The public website and authenticated customer support paths feed one Tork Control support engine; they are not separate ticket systems.