Overview
A workspace is your team's space in Spek. Store credentials, apps, drafts and agent configuration all belong to one, and nothing is shared between workspaces. Settings → Workspace is the summary: logo, name, members, connected apps, store accounts, and credits.
What belongs to a workspace
- The store credentials you connected.
- The apps you added, and their markets and competitors.
- Every draft, proposal and agent configuration.
- The people you invited, and their roles.
Roles
A member's role decides what they can change. The high-risk actions are the ones that reach a store: connecting or disconnecting a credential, and publishing.
A viewer can read the workspace but not change a connection. When an action is not available to you, the surface says who to ask rather than failing silently.
Inviting people
Invite people from Members in settings, or from the Add button on Workspace. They join the workspace you invited them to and see the apps it holds.
Common questions
Can one person be in several workspaces?
Yes, with a separate role in each. The switcher at the bottom of the sidebar moves between them.
Check the active workspace before editing, connecting a store account or reviewing billing. Access and commercial context stay separate between teams, even when the same person belongs to both. Include the workspace name in shared task descriptions so colleagues open the intended app and draft.
Does a new member see our store credentials?
They see the connected store account’s label and status. The private key is never displayed to anyone, at any role.
How should an agency organize work for separate clients?
Keep ownership, membership and store credentials aligned with the client whose apps are being managed. Separate workspaces help maintain that boundary, while each connected app retains its own drafts and Agent setup. Before inviting someone or connecting an account, check the selected workspace and the person's responsibilities. Do not reuse a client's private key across unrelated developer accounts for convenience. A clear workspace structure makes it easier to review who can see the work and who is allowed to perform supported changes.
Which role should a colleague receive?
Choose a role based on the work the colleague needs to do. Someone who only needs to read results can use read-only access, while editing, publishing, membership and billing responsibilities require the appropriate permissions. Review the actual controls available to that role instead of assuming every member can perform every task. Provider permissions still apply in addition to workspace membership. Giving someone a Spek role does not make an App Store version editable or expand the rights of the connected store credential.
What should I check before accepting a workspace invitation?
Confirm the workspace and the person or organization inviting you, then use the intended account for that team. An invitation joins an existing workspace; it should not be confused with creating a separate paid workspace for the same task. Once inside, check the selected app and your role before starting work. If the expected apps or controls are missing, ask the workspace owner to review the membership and connection context rather than sharing another person's login or store credentials.
How do I avoid mixing work between two workspaces?
Check the workspace switcher, selected app and market before reviewing drafts, managing a connection or discussing billing. Similar app names and shared team members can make the wrong context easy to overlook. In support requests or internal task descriptions, name the workspace and app explicitly. Each workspace has its own membership, credentials and commercial context, so a role or subscription in one does not automatically carry to another. A shared page link also does not grant somebody access to a workspace they have not joined.