Reviewed June 18, 2026
Setup Workflow

Owner and IT Admin Guide

Use this guide to register the organization, invite the team, set up departments, configure permissions, create projects and rituals, and prepare daily operations before rollout.

People

Departments, managers, employee onboarding, imports, and PIN accounts.

Access

Roles, permissions, project membership, and safe delegation.

Workflows

Projects, rituals, evidence, review, and operational health.

Operations

Calendar resources, docs, files, quotas, chat, voice, and notifications.
1

Register your organization

Create the workspace and first admin account when your company does not have TechOffice yet.

Example: register Docs Capture 441114 with subdomain docs-guide-441114 and admin email [email protected].

owner
it-admin
registration
sign-in

  1. Open https://transformar.work/signin/.
  2. Select Register your organization.
  3. Enter the company name and subdomain.
  4. Enter the first admin account details.
  5. Wait for the subdomain availability check.
  6. Select Create Organization, then go back to sign in after the success message.
Use a recognizable subdomain and a strong password before creating the organization.
Open

2

Confirm the active workspace

Make sure every setup action happens in the intended organization before changing settings.

Example: switch from North Star Lab to North Star Clinic before creating departments or inviting clinic employees.

owner
it-admin
organization
workspace

  1. Check the organization name in the top-left workspace header.
  2. Use the profile or organization switcher if you need a different workspace.
  3. Confirm the top navigation shows Calendar, Notifications, Chat, Tasks, Docs, Files, and Organization.
  4. Continue only after the active workspace is correct.
The workspace opens with primary navigation, search, context rail, and notification setup.
Open

3

Set up departments and managers

Build the structure used for assignment, manager visibility, search, notifications, and permissions.

Example first structure: Operations, Sales, Support, and Field Team.

owner
it-admin
departments
managers

  1. Open Organization.
  2. Select Departments.
  3. Select Create Root Department or Create First Department.
  4. Create only the top-level groups you will actually use.
  5. Add child teams when they matter for assignment, reporting, or communication.
  6. Assign managers after employee records exist.
  7. Use org chart or list view to verify that the structure is easy to understand.
The Organization page is the owner and IT admin starting point for departments, employees, and permissions.
Open

4

Invite your team members

Choose email, SSO, PIN account, or bulk import based on how each worker signs in.

Example: invite [email protected] by email, create night-shift-17 as a PIN account, and use bulk import for a store opening team.

owner
it-admin
employees
invitations
pin accounts

  1. Open Organization.
  2. Select Employees.
  3. Invite office workers with email or SSO so they can manage their own sign-in.
  4. Create org-managed PIN accounts for frontline, temporary, field, or shared-device workers.
  5. Use import for batches and review the preview table before confirming.
  6. Assign each employee to the correct department and role.
  7. Save any one-time temporary PIN before closing the result screen.
The Organization page is the owner and IT admin starting point for departments, employees, and permissions.
Open

5

Delegate with roles and permissions

Use permission-backed roles to delegate repeatable admin work without giving every operator owner access.

Example roles: People Operator, Project Lead, and Facilities Scheduler.

owner
it-admin
permissions
roles

  1. Open Organization.
  2. Select Permissions.
  3. Review who can invite employees, import employees, manage departments, manage roles, create projects, review evidence, manage resources, delete files, and change quotas.
  4. Keep owner access limited to recovery and high-risk settings.
  5. Create operator roles for repeatable administration.
  6. Use project membership for authority that should apply only inside one project.
  7. Review permissions after each rollout phase.

6

Set up projects and task workflow

Create project workspaces and keep workflow complexity small until the team needs it.

Example: create Q3 Product Launch with key PRJ56D0F and mixed mode for one-off tasks plus recurring readiness checks.

owner
it-admin
projects
tasks

  1. Open Tasks.
  2. Select New Project.
  3. Give the project a short name and key.
  4. Choose visibility: public for broad discovery, private for restricted teams.
  5. Choose collaboration mode: standard, ritual, or mixed.
  6. Add members and assign project roles.
  7. Configure states, task levels, custom fields, and workflow rules only when they clarify the work.
Tasks start from project workspaces and continue into task details, rituals, and evidence.
Open

7

Set up recurring rituals and evidence

Create scheduled operational work and require evidence only when proof matters.

Example rituals: store opening checklist, Friday safety inspection with photo evidence, and end-of-shift report with text notes.

owner
it-admin
rituals
evidence

  1. Open the project where the recurring work belongs.
  2. Create a ritual definition with a clear title and schedule.
  3. Add default assignees, departments, or reviewers.
  4. Set the completion window.
  5. Add evidence requirements only when proof matters.
  6. Save the ritual and verify upcoming instances.
  7. Use the review backlog to approve, reject, or request corrected evidence.

9

Prepare notifications, chat, docs, and files

Set up the places where daily work will happen before inviting the whole team.

Example channels: General Announcements, Operations, Q3 Product Launch, and direct messages for one-on-one coordination.

owner
it-admin
notifications
chat
docs
files

  1. Open Notifications and enable push notifications on trusted admin devices.
  2. Open Chat and create channels for teams, projects, operations, or announcements.
  3. Use private channels only for restricted groups.
  4. Create root docs for policies, handbooks, procedures, and project notes.
  5. Review file storage quotas and cleanup responsibilities.
  6. Explain when employees should use mentions, direct messages, task discussions, voice messages, and live calls.
Chat separates channels, direct messages, and task discussions so the conversation can stay with the right work.
Open