Share a diagram for review

Before you start

Prerequisites

A signed-in owner and a successfully published diagram.

Permissions and plan

Personal owners can manage public and email viewing access. Organization policy can restrict sharing.

Steps

1. Create and publish the small example below rather than using private architecture for a first test.

2. Open the diagram's sharing controls.

3. For a public link, enable public visibility. Anyone with that URL can read it.

4. For private email sharing, add the intended address. The recipient must sign in with the matching email.

5. Save access, then verify the URL with a separate authorized recipient session. To revoke access, remove the recipient or disable public visibility and save again.

Copy this model into Import in the editor. Export current work first. The two stable identifiers, api and db, connect the services to the flow.

# Request path

- API {#api type=service x=100 y=120}
- Database {#db type=database x=500 y=120}

## Flows
- api -> db {#requests label="requests" color=#f05a47 speed=1 direction=forward}

Change a label to describe your system. Keep the identifiers the same when you want existing connections to keep referring to those nodes.

Check your work

Expected outcomeAn intended reviewer can view the diagram with the access you chose.

Next steps

Try the workflow in the editor, then use the reference for control details and model syntax.

If a step does not work, keep an export of your model and follow the troubleshooting guide. Include the error message when contacting support, without sharing credentials or private architecture.