Workspaces, members & API keys
A workspace is the container for everything you do in Taskbox - the tasks your automations push in, the teammates who resolve them, and the API keys your tools use to connect. This doc walks through setting one up and keeping it tidy.
About workspaces
When you sign up, Taskbox creates your first workspace automatically. You can create more at any time from the workspace switcher - useful for separating environments (staging vs. production), client accounts, or distinct teams. Each workspace has its own members, its own API keys, and its own tasks; nothing crosses between them.
Switch between workspaces from the sub-nav under Tasks. The dashboard you see is always scoped to the workspace you've selected.
Roles
Every member of a workspace has one of three roles. Roles are per-workspace - someone can be an owner of one workspace and a plain member of another.
Full control. Manages members and roles, creates and revokes API keys, edits workspace settings, and is the only role that can archive the workspace or transfer ownership. Each workspace has exactly one owner.
Owner-lite. Invites and removes members, manages API keys, and configures the workspace. Cannot archive the workspace, cannot remove or demote other admins, and cannot promote a member to admin - those are reserved for the owner.
Day-to-day user. Sees the task list, opens task detail, and approves or rejects tasks they're assigned to. No access to settings or keys.
Inviting members
Owners and admins can invite teammates from Settings → Members. Enter an email address and pick a role - the invitee can finish setting up their account on their next visit. Until they do, they show as Invited in the member list and can't yet resolve tasks.
Workspaces have a member cap under our fair-use policy. If you're at the limit, the invite button is disabled and the members page tells you what's available.
Managing members
From the same Members page, owners and admins can:
- Remove a member - they immediately lose access to the workspace and any tasks assigned only to them are unassigned.
- Change a member's role - only the owner can promote a member to admin or demote an admin back to member.
- Transfer ownership - the current owner hands the role to another member, becoming an admin in the process.
Removing yourself from a workspace is allowed only if you aren't the owner. To leave a workspace you own, transfer ownership first or archive the workspace.
API keys
API keys are how external systems - your agents, n8n flows, scripts - authenticate when pushing tasks into Taskbox. Each key belongs to a single workspace; tasks created with it land there.
Owners and admins manage keys from Settings → API keys. Give each key a descriptive name (e.g. n8n-prod, refund-bot) so you can tell at a glance which integration uses it.
When you create a key, Taskbox shows the key value and its signing secret once. Copy them straight into your tool's configuration - you won't be able to view them again. If a key leaks or you lose it, revoke it and create a new one. Revocation takes effect immediately.
The keys list shows each key's name, when it was created, and when it was last used, so it's easy to spot keys you no longer need. We recommend rotating keys whenever someone with access leaves the team.
Archiving a workspace
When a workspace is no longer needed, the owner can archive it from the workspace settings. Archived workspaces are read-only: existing tasks stay visible, but no new tasks, members, or keys can be added, and any API keys stop working. Archiving is permanent - there's no un-archive - so use it only when you're sure.
Next steps
Once your workspace has the right people and at least one API key, head over to Create tasks via API to start sending tasks in.