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
| Who | Role | Why |
|---|---|---|
| Everyone who produces work | Member | Needs create and edit in shared spaces |
| Team leads | Space owner | Manages members and files of their own space only |
| IT or ops, one or two people | Admin | Invites and quota, but not personal file access |
| Client or contractor | Guest | Access to a specific folder, nothing else |
The five-item checklist
- 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.
- Move shared patterns into agents
If three people use the same prompt, it belongs in a shared agent, not in three notebooks.
- Write down who owns the quota
Quota is per workspace. When it runs out mid-month, someone needs the authority to decide who waits.
- Review external shares monthly
Removing a member does not revoke links they already sent. Reviewing shares is a separate task.
- 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
- Remove from the workspace first; this cuts access to shared spaces immediately.
- Then review shared links created by that account — they remain live until revoked.
- Personal space files are not transferred. If the work mattered, it should have lived in a shared space.