Read the request header
The request header brings together the title, service, status, priority, target date, matched designer, and participant context. Open the request instead of relying on the smaller board card when a decision depends on details.
Join or share the request
- Join when you are participating in the brief, feedback, or approval
- Copy the request link when sending someone to the exact context
- Invite the person to the workspace before sharing an authenticated link
- Leave the request when you no longer need its participation signals
Use activity as an audit trail
Activity records meaningful events such as creation and status movement. Comments explain the decision behind the event, while the brief holds the current accepted direction.
Use the detail view for decisions
The board card is a summary. Open the request when you need the full brief, service, priority, target date, matched designer, members, files, comments, or delivery context. Copy the request link when another teammate needs to land on the same record.
Members and history solve different problems
Request members show who is involved in that work. Comments preserve the discussion and accepted feedback. Status and metadata show the current operational state. Joining a request does not grant a different workspace role, and leaving one does not erase earlier activity.