Roles and permissions

Everyone participates at the level matching their role.

Four roles, three internal and one external, each with a clear scope. And Contacts, for the people your work involves who don't use Thingz at all.

Roles and profiles

What each role can do

Admin Internal

Runs the workspace. The only role that can touch billing, integrations, and workspace-wide settings. The only one that can remove a user or grant Admin to someone else. Otherwise unrestricted on which hacktions or memos they can see or edit.

One limit on their own account: cannot change their own role, and no one can remove their own account, ever, including an Admin.
Project Manager Internal

Runs the day-to-day work. Their reach is scoped: they can see a plan's hacktions only if they own it, are assigned a hacktion in it, or created one in it. Can invite new people (Member or Stakeholder only), create work for others, and see the workspace directory.

Can only edit or delete hacktions they personally created. Cannot touch billing, integrations, grant Admin access, or remove a user.

Limit: scoped to plans they are involved in. Edit and delete limited to hacktions they created. Locked out of billing, settings, and user removal.
Project Member Internal

Does the work. Sees every hacktion in plans they are part of and can update the status of items assigned to them, through the app, Teams/Slack, or the bot. Can create memos.

Cannot create hacktions, cannot edit beyond the status of assigned items, cannot see the workspace directory. Carson in the web app is not yet available; Teams/Slack bot access is full.

Limit: status updates on assigned items only. No workspace directory. Web app AI restricted for now.
Stakeholder External

An external participant looped in on a specific commitment. Sees only hacktions assigned to them. No memos, no workspace directory. Carson access is limited (Teams/Slack only, no web app, no proactive check-ins).

Can accept, update status of, or comment on their assigned hacktions through the app, Teams/Slack bot, or notification cards. Gets notified when something involving them happens.

Limit: assigned hacktions only. No memos. Limited Carson (Teams/Slack only). Counted separately from your team size.
Contact No account

Someone your work involves who doesn't use Thingz: a person named in meeting minutes, a supplier, a colleague in another department. A Contact can own a hacktion or a memo item, so the work is tracked under their name.

Contacts have no login and receive no notifications from Thingz, only the meeting minutes email. Following up with them stays with your team. They are not counted in your team size.

Limit: no access, no notifications. 20 Contacts per internal seat, shared across the workspace. At the limit, nothing is blocked: the name stays as plain text.

About team size: Admin, Project Manager and Project Member all count toward your team size. Stakeholders are counted separately, as external users. Contacts are not users and are never counted.

Each internal seat you pay for includes 1 Stakeholder slot, 20 Contacts shared across the workspace, and its share of the monthly AI allowance.

For instance: a team size of 10 gives you 10 internal users, 10 Stakeholder slots, 200 Contacts and a monthly AI allowance generous enough for everyday use. Need more Stakeholder slots? Contact us.

Full breakdown

Permission table

Capability Admin Project Manager Project Member Stakeholder
User type
User type Internal Internal Internal External
Hacktions
View hacktions assigned to them ✓ ✓ ✓ ✓
View every hacktion across the workspace ✓ Owned plans or plans they are involved in Plans they are involved in Assigned only
Update status of a hacktion assigned to them ✓ ✓ ✓ ✓
Edit other fields (title, due date…) on a hacktion assigned to them ✓ ✓ — —
Create hacktions ✓ ✓ — —
Edit hacktions they did not create ✓ Created only — —
Delete hacktions ✓ Created only — —
Memos
Read any memo ✓ ✓ ✓ —
Create or edit memos ✓ ✓ ✓ —
Workspace
See the team-wide dashboard ✓ ✓ — —
Invite new people ✓ any role Member or Stakeholder only — —
Change someone else's role ✓ any role Member/Stakeholder only, cannot grant Admin — —
Remove a user from the workspace ✓ except self — — —
Edit own profile ✓ ✓ ✓ ✓
View the workspace directory ✓ ✓ — —
Billing and settings
Billing, subscription, workspace settings ✓ — — —
Buy additional AI usage credit ✓ — — —
Connect or manage integrations ✓ Read status only — —
Carson
Use Carson in the web app ✓ ✓ Coming soon —
Use Carson via Teams/Slack bot ✓ ✓ ✓ Limited
Notifications
Receive notifications on items assigned to them ✓ ✓ ✓ ✓
Status change notifications follow a relationship-based rule, consistent across all surfaces and roles:
  • The creator changes status: the assignee is notified.
  • The assignee changes status: the creator is notified.
  • Neither the creator nor the assignee changes it: both are notified.
  • The same person is both creator and assignee: no one is notified.
Carson

Carson settings and access

Carson is configured at two levels: workspace-wide settings controlled by Admin only, and personal preferences each internal user manages for themselves. Stakeholders have limited access to Carson, through Teams and Slack only.

Capability Admin Project Manager Project Member Stakeholder
Access to Carson ✓ ✓ ✓ Limited
Turn Carson on/off ✓ — — —
Change Carson default schedule ✓ — — —
Opt in/out of Carson automatic updates ✓ ✓ ✓ —
Set personal Carson schedule ✓ ✓ ✓ —
Receive Carson proactive check-ins ✓ ✓ ✓ —
Start your free 30-day trial

No credit card required. Early bird 2026 pricing locked for 12 months.