Skip to main content

Workspace and Collaboration

If more than one person is using the same workspace, collaboration needs structure.

You are not just sharing static views. You are sharing a live workspace with AI team members, connections, approvals, ongoing tasks, and change history.

What sharing a workspace really means​

When you add someone to a workspace, you may be giving them access to:

  • the views
  • workflow and activity history
  • service connections
  • AI team settings
  • approval responsibilities
  • shared view controls

That is why membership is not a casual action.

Common workspace roles​

Workspaces usually need a small set of role types.

Owner​

Use this role for the person who has final control.

An owner typically controls:

  • membership
  • major workspace settings
  • destructive actions
  • sensitive capability decisions

Admin​

Use this role for trusted people who help manage the workspace.

An admin typically manages:

  • members
  • connections
  • workflow configuration
  • shared views

Member​

Use this role for people who actively use the workspace and may help shape the work, but should not have full management power.

Viewer​

Use this role for people who need visibility without editing or management rights.

How to choose the right role​

Ask one question:

What should this person be able to change without asking someone else first?

If the answer is “only their own use of the workspace,” they probably do not need admin-level access.

If the answer is “team setup, sharing, and policy-sensitive changes,” they probably do.

What to agree before inviting more people​

Before a workspace becomes shared, agree on:

  • who owns the workspace
  • who approves new packs or risky capabilities
  • who manages service connections
  • who reviews major changes before publication
  • which AI team members may act automatically

If you skip that conversation, the workspace usually becomes unclear as soon as it starts evolving.

Day-to-day collaboration​

In practice, collaboration often looks like this:

  1. one person asks Worka to add or change something
  2. another person reviews the plan
  3. someone approves a new connection or sensitive action if needed
  4. the team starts using the updated view as it arrives
  5. AI team members continue handling routine work in the background

That rhythm is normal. A workspace is supposed to keep moving after the first delivery.

What people should be able to see​

Shared ownership only works if people can tell what is happening.

In a healthy workspace, the right people can see:

  • what Worka is building
  • what changed recently
  • what is waiting for approval
  • which AI team members are active
  • which connections and shared views exist

If important activity is hidden, collaboration quickly turns into guesswork.

A simple workspace health check​

A shared workspace is in good shape when a new team member could answer:

  • what this workspace is for
  • who approves sensitive changes
  • which views matter most
  • where to look for blocked work
  • who manages services and sharing

If they could not answer those in a few minutes, the workspace roles or layout still need tightening.