Set boundaries before you share

Share only the context needed

Choose the smallest audience that fits the task. Before Production, ask who will attend, what will be captured, where files will go, who can approve changes and how private details will be protected. Do not send passwords, card numbers, bank details or identity documents through a public profile or casual message.

If a location, subject or project is sensitive, say what access is required and who holds responsibility. Clear context gives a collaborator a real chance to consent or decline.

• Check audience and access before sharing.
• Confirm people, place, capture and storage.
• Keep financial and identity secrets out of chat.

Use boundaries as an active choice

You can pause a request, ask for more information, decline a scope, unpublish a portfolio or stop a conversation. You do not need to justify a boundary with a dramatic explanation. If a person has asked for no contact, respect it.

Keep unresolved scope, attendance or delivery concerns in the project record when it is safe to do so. A structured pause can prevent a rushed decision from becoming a larger problem.

Report and block with context

Use report for spam, harassment, impersonation, rights concerns or unsafe conduct. Add the page, project or message involved and enough detail to understand what happened. Block new contact when you need distance.

A report is a request for review. Its outcome depends on the evidence and applicable rules; it does not guarantee a particular decision or response time. Block unwanted new contact when needed. In an immediate emergency, contact the appropriate local emergency service.