Permissions

QwenWorkPermissions before the team arrives

Ten minutes of setup prevents the two failures that are expensive to undo: private drafts visible to admins, and shared links that outlive the person who created them.

Role assignment, in one table

WhoRoleWhy
Everyone who produces workMemberNeeds create and edit in shared spaces
Team leadsSpace ownerManages members and files of their own space only
IT or ops, one or two peopleAdminInvites and quota, but not personal file access
Client or contractorGuestAccess to a specific folder, nothing else

The five-item checklist

  1. Decide the workspace before inviting

    Personal space is the default on first sign-in. If the team should land in the organisation, say so in the invitation.

  2. Move shared patterns into agents

    If three people use the same prompt, it belongs in a shared agent, not in three notebooks.

  3. Write down who owns the quota

    Quota is per workspace. When it runs out mid-month, someone needs the authority to decide who waits.

  4. Review external shares monthly

    Removing a member does not revoke links they already sent. Reviewing shares is a separate task.

  5. Name an automation owner

    Every scheduled task needs one person who reads its failure reports.

What admins can and cannot see

Admins see usage, model access settings, member lists and shared-space contents. They cannot open an individual's personal space. That boundary is deliberate — it is what makes it reasonable to keep drafts there. Plan around it: if something must be auditable, it belongs in a shared space from the start, not in someone's personal area.

Offboarding

Guests are the usual leak. A guest with access to one folder can still screenshot it. If the content is sensitive, the control is not the permission model but whether the person should see it at all.
How the layers separate: workspace overview.