Skip to main content
llms.txt

Integration permissions and API-key ownership

Understand who can connect Slack and MCP, publish space jobs, create or revoke API keys, and what happens when roles, subscriptions or credentials change.

To manage jobs for a space, you need to be its owner or a Team Member on Coworkies. If you hire without a space, choose My own jobs to manage jobs you posted independently. Installing the app as a Slack administrator gives you no additional access on Coworkies.

Who can do what?

Person or credentialConnect and manage space jobsCreate space API keys
Verified individual hiring managerPersonal jobs only: the same creator and no attached space. No Pro requirement.Use account connection; no self-service personal API key.
Coworkies space ownerYes, for their eligible space and granted scopes.Yes, for a confirmed Pro space they manage.
Coworkies Team Member with staff roleSame space job authority as the owner, including jobs created by other Team Members.Yes, for a confirmed Pro space they manage.
Ordinary coworking space memberNo automatic management or publishing rights.No space-management key authority from membership alone.
Slack member, administrator or app installerInstallation/membership grants no Coworkies authority. Each publisher connects separately.No authority from their Slack role.
Holder of a valid ordinary space keyCan exercise the key owner’s permissions. Native Slack key entry does not separately authenticate the holder’s Coworkies login.Holding a key alone does not grant the website account’s key-management rights.
Platform administrator or approved importerSeparate, explicitly controlled server privileges; normal connectors do not confer them.Platform administration follows separate rules.

Account-based connection requires an active, verified account. Personal hiring needs no space. Space hiring additionally requires a current owner/Team Member relationship to a confirmed space. Being employed by the company does not itself create the staff relationship in Coworkies.

Access differs by integration

RouteSpace selection and access
REST ordinary space keySpace-bound operations follow the key’s space, scopes and owner’s current authority.
Slack account connectionChoose My own jobs or an eligible confirmed managed space. No Pro requirement; one hiring account per Slack member/workspace.
Slack native API-key connectionThe key selects the space and delegates its owner’s authority. Read/write job permissions are required.
MCP OAuth discoveryActive, verified account with the discovery scope.
MCP OAuth private jobsChoose My own jobs or one confirmed, open space you currently manage. Grant the job actions the client needs.
MCP direct API keyPublic discovery only, even when the key can write through REST.

Who can create, view, rotate and revoke keys?

  • A space owner or Team Member can create a key for a confirmed Pro space they currently manage. Ordinary non-space keys cannot manage jobs.
  • The account limit is 10 active, unexpired keys, including assistant credentials.
  • The complete ordinary key is shown only when created or rotated. Space managers can view key metadata, not recover its secret.
  • Only the key creator can rotate it. Rotation revokes the previous secret; update clients immediately.
  • The key creator or a platform administrator can revoke it. Being the space owner does not automatically let you revoke another Team Member’s personal key.
  • Only a platform administrator can issue admin scope. A key prefix or integration name never establishes authority.

You need a confirmed Pro space you manage to create or rotate a manual space key. If Pro coverage ends, those keys pause. If a rotation fails, the existing key is unchanged. To connect Slack or MCP without a manual key, sign in with your Coworkies account and review the requested permissions.

Use Create and manage API keys for the UI steps. Use GET /v2/auth/key to inspect a key’s effective scopes and space through the authenticated REST API.

Scope does not replace ownership

jobs:read and jobs:write, or their supported parent scopes, control REST job operations. Space membership and current account/key validity are checked as well. spaces:write and offers:write require explicit scopes; broad write does not include them. MCP also checks the adapter’s enabled tools and the current OAuth grant.

Choose My own jobs to manage jobs you created without a space. With separate Slack consent, a private list can also show active jobs the same user authored in spaces they still manage. This read does not switch the posting account. A space manager can manage the connected space’s jobs, not another space’s. To access personal jobs, connect your Coworkies account and approve access. A job’s contact email does not confer ownership. Keys should be dedicated to one purpose and publisher; sharing a manager’s key deliberately delegates that manager’s authority.

Shared personal limits

Your Slack and MCP connections share a limit of 20 personal hiring requests per minute and 1,000 per UTC day, including identity checks. Reconnecting or changing keys does not reset it. These limits are separate from paid job credits and public search limits.

Permission to submit is not guaranteed publication

If your account has no hiring credit available, a paid job stays in draft until you complete checkout on Coworkies. Check the status after submitting and follow any payment link. See Space plans.

What happens when access changes?

ChangeEffect
Key expires or is revoked; account disabledSubsequent authorized operations fail. OAuth refresh is also blocked when its credential/account is invalid.
Key owner loses management rolePrivate space operations stop.
Space loses ProOrdinary manual space tokens pause. Account-connected Slack and MCP hiring still require the selected account, current role and granted actions. Privileged space operations can require current Pro.
Slack account connection is disconnectedEach colleague stays connected and your published jobs remain visible.
Native Slack key connection is disconnectedThe stored copy is removed; the original key remains active.
One MCP OAuth grant is revokedOther clients’ separate grants remain independent.
A request was already sent before disconnectDisconnect cannot recall an in-flight write. Reconcile the result before retrying.

Keep credentials out of messages, screenshots, logs and URLs. For setup and recovery, see Slack and MCP.