Secure Map Sharing Guide: Roles, Passwords, Expiry, Revokes

Sharing a map should be quick, but never loose.

In Mindmap Maker, you can create secure share links with controlled permission, optional expiry, and optional password protection.

Mindmap-Maker also gives you explicit recovery controls: copy, regenerate (rotate token), and revoke.

These sharing controls are part of the free experience for all users.

Quick answer

For secure collaboration, use this default flow:

1. Create a VIEWER link first.
2. Add expiry for time-bound access.
3. Add password for sensitive maps.
4. Upgrade to EDITOR only for trusted collaborators.
5. Rotate or revoke links as soon as access scope changes.

Open the editor: Start mapping

1) Permission model: what to use and when

The share modal link creation flow supports two link permissions:

• VIEWER
• EDITOR

Practical guidance:

• Use VIEWER for review, approval, and read-only circulation.
• Use EDITOR when collaborators must update map content directly.

Important detail:

• The broader platform permission model includes OWNER, but share-link creation in the invite flow is explicitly viewer/editor oriented.

2) Add security controls at link creation time

When creating a share link, you can set:

• Expires at (optional datetime)
• Password (optional)

Behavior reflected in the link list:

• Expiry is shown per link (No expiry when not set).
• Password status is shown (Password protected or No password).

Use both controls together for high-sensitivity maps:

• Password controls who can open.
• Expiry controls how long that access remains valid.

3) Day-2 access operations: copy, rotate, revoke

Each active link row provides three direct actions:

• Copy link
• Regenerate link (rotate access token)
• Revoke link

Operational best practices:

1. Rotate links after external forwarding risk.
2. Revoke links immediately when a collaboration window closes.
3. Recreate fresh links instead of reusing old tokens across unrelated projects.

Useful implementation detail:

• If a token URL is not currently available in session state, regenerate once and copy the new link.

4) Embed publication is separate from invite links

The share modal also includes an Embed tab with publication controls.

Embed flow supports:

• Publish/unpublish embed
• Update published embed to current map revision
• Copy embed link and iframe code
• Publication status checks (up-to-date vs out-of-date)

Why this matters:

• Invite links are for controlled collaborator access.
• Embed publication is for broader read-oriented distribution contexts.

Treat these as different channels with different risk levels.

5) Token-based sharing workflow that scales

Use this repeatable handoff pattern for teams:

1. Start with viewer link + expiry.
2. Add password if content includes sensitive planning details.
3. Share only the minimum necessary editor links.
4. Rotate links after major milestones.
5. Revoke stale links during project closeout.

This keeps access predictable while avoiding over-permissioned long-lived links.

Common sharing mistakes and fixes

Mistake: defaulting to editor access for everyone

Fix: create viewer links first, then issue editor links only where active contribution is required.

Mistake: sending long-lived links without expiry

Fix: set expiry by default, especially for external or cross-team distribution.

Mistake: forgetting to revoke links after the project phase ends

Fix: include revoke checks in sprint close or milestone handoff routines.

Mistake: treating embed publication like collaborator access

Fix: use invite links for controlled collaboration and embed only for intentional public-style consumption.

Related guides

• Prepare clean deliverables in Mind Map Export Guide: PNG, PDF, Word, and HTML Outlines.
• Improve map readability before sharing with Mind Map Styling Guide: Themes, Node Design, Readability.
• Recover from access or workflow issues in Fix Common Mind Map Issues: Sync, Performance, Missing Edits.

Final takeaway

Secure collaboration is less about one perfect setting and more about disciplined link lifecycle management.

Set the minimum permission, add expiry/password where needed, and actively rotate or revoke links as collaboration context changes.