Skip to content

Workspace access (users & roles)

Sertiq has two separate lists of people that often get confused. They serve different purposes — read this once and the distinction sticks.

Settings → Workspace accessOrganization → Employees
People who log in to SertiqQuality team headcount
Roles: admin / editor / viewerJob title, department, skills, certifications
Counts against membersMax plan limitCounts against employeesMax plan limit
Receives email invitation + sign-in credentialsDoesn’t need to log in — pure HR-style record
Example: CEO, QA Manager, Plant ManagerExample: line operators, warehouse staff, external inspectors

If someone needs both (e.g. the QA Manager who logs in and shows up on 8D teams), add them to both lists. Linking is optional — when set, employees.user_id ties an employee record to a workspace user.

Admin-only page that controls Sertiq sign-in.

RoleWhat they can do
AdminEverything: invite/remove members, change roles, edit org profile, change plan, configure issue types, view billing, full CRUD on all data
EditorCreate + edit suppliers, NCRs, CAPAs, evaluations, RMAs, calibration. Cannot manage workspace or billing.
ViewerRead-only. Useful for auditors, external consultants, executives who want to monitor without risk of edits.
  1. Admin opens /settings/users
  2. Enter email + role → Send invite
  3. Invitee gets an email with a 7-day signed link
  4. Clicking the link → sign-up form (email pre-filled) → account created, joined to the inviter’s organization

Invitations appear under Pending invites until accepted or expired. Admins can Revoke at any time.

Inline dropdown next to each member → Change role. Effect is immediate. There must always be at least one admin — demoting the last admin is blocked.

Click Remove next to a member. Their data (NCRs, CAPAs they created) stays under their name; they lose access. Removing yourself is blocked — ask another admin.

Your operational org chart — every person who works at your company, whether or not they touch Sertiq directly.

When you’d add an Employee but not a Workspace user

Section titled “When you’d add an Employee but not a Workspace user”
  • Line operator named on a 5-Whys investigation
  • Warehouse picker mentioned in an NCR description
  • External calibration technician
  • New hire who hasn’t been onboarded to Sertiq yet
  • People you reference in CAPA assignments via name + email only
  • Full name, email (optional), phone
  • Job title, department, reports-to (manager hierarchy)
  • Skills (e.g. ["GD&T", "Welding L2", "ISO 19011 lead auditor"])
  • Certifications (e.g. [{ "name": "Six Sigma Green Belt", "expires": "2027-03-01" }])
  • Hire date, status (active / on_leave / inactive)
  • user_id — optional FK to auth.users, set when an Employee is also a Workspace user

Under /organization/departments. Each employee belongs to one. Departments power:

  • Employee filtering
  • Ownership grouping in analytics
  • CAPA assignment routing by department

The two lists are gated separately:

PlanmembersMax (workspace)employeesMax (org headcount)
Free13
Starter315
Pro1050
EnterpriseUnlimitedUnlimited

At the limit, Add is replaced with Upgrade to add more.

“I added someone to Employees — why can’t they log in?” The two lists are independent. Send them a Workspace invitation from /settings/users.

“Can I import employees from CSV?” Not yet — manual entry only. CSV import is on the v1.3 roadmap.

“Does removing a workspace member also remove their Employee record?” No. Workspace removal only revokes login. The Employee record (if any) stays for historical traceability.