# CS-35: Team permissions and safe offboarding

Category: Work & enterprise tools
Level: Advanced
Suggested duration: 4–6 weeks

Original UXCharan practice scenario. Validate assumptions; do not present it as a commissioned client project.

## Problem
A hypothetical collaboration product makes it difficult to see which access a role grants. Explore invitations, access changes and offboarding with clear consequences and recoverable mistakes.

## People to learn from
Workspace administrators managing employee access

## Core scope
- Invite a member
- change access
- transfer ownership

## Research questions
- How do admins review existing access?
- What must happen before removing an owner?

## Edge cases
- Last owner removal
- expired invite

## Specific artefact
A role matrix and confirmation patterns

## Evaluation question
Can admins predict the consequences of an access change?

## Work to share
Problem and role; anonymised evidence; alternatives and rationale; task flow; prototype; accessibility considerations; testing findings; revisions and honest limitations.

## Request feedback
Share a viewable Figma, document or portfolio link with Saicharan on WhatsApp: https://wa.me/917093809350
Include CS-35, your name, project stage and your main feedback question. Confirm review scope, timing and any fee directly.

## Methods
- Research planning: https://www.gov.uk/service-manual/user-research/plan-user-research-for-your-service
- Research consent: https://www.gov.uk/service-manual/user-research/getting-users-consent-for-research
- Design exploration: https://www.designcouncil.org.uk/resources/the-double-diamond/
- Usability testing: https://www.nngroup.com/articles/usability-testing-101/
- Accessible forms: https://www.w3.org/WAI/tutorials/forms/
- Portfolio storytelling: https://www.nngroup.com/articles/ux-design-portfolios/