What you will take away from this lesson
Article 302 ended with a shortcut: ask for a link when the agent runs an export, and the export comes back with one. This article covers the whole sharing system. It works the same way for a dashboard from 301, a report, a chart, an export from 302, a collection, a prompt, and a file.
Everything happens in one dialog. You add people or groups, you decide who else can open the item without being added, and you post it to the channel where your team already talks. Someone who follows a link they cannot open asks you for access, and you answer from wherever the request reaches you.
Learning Objectives
- 01Read the Share dialog as four parts: who you add, who has access, the general link, and the channels the item was posted to.
- 02Choose between a person, a group (a persona), and a guest, and say what each one can do once they open the item.
- 03Change or remove someone’s access in place, and use Undo when you removed the wrong row.
- 04Set the general link to only people added, anyone who can sign in, or anyone with the link, knowing that changing it keeps the URL.
- 05Post an item to a Slack, Mattermost or email channel as a link you can take back later.
- 06Answer a request for access from the email, the Inbox, or the dialog itself.
- 07Share a file the same way you share an asset, and know where the sharing permission comes from.
Where this lesson sits in the curriculum
301 built dashboards and reports. 302 produced data exports. Both produce assets that live on your Assets page. 303 is how those assets get into a teammate's hands, into a team channel, or in front of a reader with no Plexara account at all.
300 Series: getting more out of Plexara
- 301Creating reports and dashboardsHow to ask the agent for shareable work product instead of chat that scrolls away. What happens when you save, and the habits that decide whether your dashboard survives next week.
- 302Exporting dataWhen you need a spreadsheet a teammate can sort, or a data file for another system, instead of a view.
- 303Sharing your workOne Share dialog for people, groups and guests, one general link whose audience you can change without changing the URL, posts to a Slack, Mattermost or email channel, and requests for access you approve in place.
- 304Creating collectionsBundle a dashboard, a summary, and the underlying data into one navigable briefing. Build it during the session via the agent, or by hand on the portal's Collections page.
- 305Editing what you already haveName the part you want changed and the agent edits that piece in place. Ask what is in a report, compare two versions, and keep shared links working. Metadata edits do not bump the version; content edits do; revert is append-only.
- 306How an asset was builtThe audit trail Plexara records at the MCP boundary: which tool calls the agent invoked, with what parameters, in the producing session. Captured at save time, readable by you or the agent.
- 307Turning a comment into something the agent remembersA reviewer opens a correction on your dashboard, an agent folds it into the knowledge loop with memory_capture thread_ids, and the person who raised it confirms or disputes the resolution. Worklists keep the open ones visible; manage_feedback works the whole backlog in one pass.
- 308Reproducible promptsSave the starting instruction as a first-class prompt with named arguments via Manage Prompts (manage_prompt). Re-run it later with different values. Personal, persona, or global scope. What re-running does and does not guarantee.
The 300 series is practical recipes for working with Plexara day to day. It assumes the mental model from 205.
The Share dialog
Share on any asset, collection, prompt or file opens the same dialog. It answers one question, who can open this item, in four parts, and every change you make in it applies at once.
The Share dialog, top to bottom
- 01
Add people or groups
Who else should have this?
A search box over the user directory and the personas. Typing lists matching groups, with how many people each reaches, and matching people. A full address nobody in the directory has is offered as a guest. Anyone who already has access is marked Has access and cannot be picked twice.
- 02
People with access
Who has it now?
The owner first, then each person and group in the order they were added, each with a menu that changes what they can do or removes them.
- 03
General access
Who can open it without being added?
One setting for the item’s one general link: only people added, anyone who can sign in, or anyone with the link until a date you pick.
- 04
Posted to channels
Where has it been posted?
Each channel the item was posted to, with how often that post’s link was opened, and Remove to stop it opening.
The footer holds three buttons: Copy link, Post to a channel and Done. Copy link copies the general link, or the item's own portal page when there is no general link, which opens only for the people with access.

People, groups and guests
Typing in Add people or groups searches the user directory and the personas together. What you pick decides who the share follows: one person, a team whose membership changes over time, or one outside address with no account.
Three kinds of recipient
A person
Listed from the user directory as you type a name or an address.
Can view or Can edit, as you choose.
The share opens only for that person, signed in. Forwarding the email or the URL gives nobody else anything.
A group
A persona, listed under Groups with how many people it reaches now.
Can view or Can edit, for every member.
Membership is read each time someone opens the item. A person who joins the persona later can open it, and a person who leaves cannot, with no change to the share. It is listed once, by the persona’s name and size.
A guest
A full email address nobody in the directory has.
View and download only.
A guest has no account and opens the item through a single-use link emailed to the address you named. Can edit is disabled while a guest is among the recipients.
A group is the right choice when the audience is a team rather than a list of names. The share follows the team as people join and leave it, so nobody has to remember to update it.
Adding people
Picking a recipient switches the dialog to Adding people. Add as many recipients as the work needs, choose what they may do, and decide whether they get an email with your note.
Adding people: every control, and what it decides
Recipients
one chip per person, group or guest
Pick as many as you need before sharing. Addresses pasted in the Example User <[email protected]> form a mail client copies are reduced to the bare address, so what is stored and mailed is what you see.
Can view or Can edit
one choice for all the chips
Can view opens and downloads. Can edit also changes the item. A guest can only view, so Can edit is disabled while one is among the chips.
Send an email
on by default
Turn it off to share quietly. The share is made either way. Leaving it on does not force a message either, because each recipient’s own notification settings decide whether and when it arrives.
Message
optional, up to 500 characters, plain text
Quoted in the email and attributed to you. It travels only in that email. Markup and links are refused rather than delivered, because a plausible link inside a trusted platform email is a phishing vector.
Share
one share per chip
A recipient who cannot be shared with stays as a chip with the reason under it, and everyone else is shared with.


Changing or removing access
People with access is a working list, not a record of past decisions. Each row is changed where it sits.
General access and the one link
An item has one general link, and General access sets who it opens for. Starting with the narrowest audience that does the job is the least-privilege starting point that runs through the whole platform.
General access: one link, three settings
Only people added
Opens for: The people and groups listed, and nobody else.
Lasts: No link exists.
The setting for anything you are sending to named people. Copy link then copies the item’s portal page, which opens only for them.
Anyone who can sign in
Opens for: Any signed-in user of your deployment who holds the link.
Lasts: Until you change it.
The right setting for an internal link. A colleague who finds it on a wiki page can open it; nobody outside your sign-in can.
Anyone with the link
Opens for: Whoever holds the link, with no sign-in at all.
Lasts: An hour, a day, a week or thirty days, then it stops working.
At this setting the link is the whole credential, so it always stops working at the time you pick. The page can also show the date it stops working.
Choosing a setting applies it at once, and the link keeps its URL. A link already pasted into a ticket or a thread follows the new rule, so narrowing who can open it never means handing out a new one. While there is a link, you can also set the banner shown on the shared page. Every request behind the link is checked against the setting before anything is served, the same decision at execution time the platform applies everywhere else.


Posting to a channel
Most work gets discussed in a team channel. Post to a channel sends the item to a Slack, Mattermost or email channel with a preview and your message, as a link you can take back later. Posting is also how an automation publishes its results, covered in 608.
Post to a channel: who the posted link opens for
Anyone who can sign in
The post carries a link any signed-in user can open. Posting the same item to the same channel again reuses it.
Anyone with the link
The post carries a link anyone can open until the time you pick. The right choice only for a channel that includes people with no sign-in.
Only people with access
The post links to the item’s page and shares nothing. Readers of the channel who already have access open it; everyone else can request access.
The channels offered are the Slack and Mattermost channels your workspace bot is in and the email lists and other channels you can reach. You add an optional message and see a preview of what the channel will show before you post. Each post is its own link, listed under Posted to channels with how often it was opened, and Remove there stops that link from opening. The message in the channel stays; the link in it no longer opens anything.

Requests for access
A link reaches people you did not add: forwarded in a thread, pasted in a ticket, found in a channel. When one of them cannot open it, they ask you, and you answer without opening the dialog to type their address.
A request for access, from the link to the answer
- 01
They follow a link they cannot open
The person asking
A signed-in colleague sees You do not have access to this item, who owns it, and Request access with room for an optional message.
- 02
The request reaches you
You, the owner
By your own notification settings: an email, and a line under Access requests at the top of your Inbox. The item’s Share dialog lists it too.
- 03
Approve as viewer, approve as editor, or decline
You, the owner
From the email, the Inbox, or the dialog, whichever you reach first. Approving shares the item with them, so the link they followed opens with no further step.
- 04
They hear the answer
The person asking
Either answer is emailed to them. A declined request can be asked again later.
A person has one request waiting per item; asking again while it waits notifies nobody. Each person can ask for one item at most three times a day, and a request nobody answers expires after the period an administrator sets under Admin > Settings > Access requests, which also decides whether the request page names the item. Administrators see and answer every request. Requests work the same way for assets, collections and prompts.


What the recipient receives
Leave Send an email on and your recipient gets a message that explains itself and opens the work in one click. The parts below make it worth sending and worth trusting on the other end.
What lands in the recipient's inbox
A link to the item itself
The message opens on the exact dashboard, report, or collection you shared, not on a portal home page the recipient then has to search. For a stakeholder who opens Plexara twice a quarter, that decides whether your work gets read on the spot.
Your note, quoted and attributed to you
The message you typed is rendered as a quoted block with your name on it. "Here is the Q3 revenue breakdown you asked about" answers the question a bare link leaves open: why am I receiving this?
A way out that needs no login
The unsubscribe link in the footer works without signing in, and so does the unsubscribe button the recipient's own mail client offers. The footer link opens a confirmation page with one button rather than opting anyone out on the spot, because corporate mail security opens links before a person ever sees them.
Mail that reaches the inbox
It renders in the mail clients your recipients use, threads properly when they reply, and carries the sending details that keep filters from treating it as junk.

Guests
A guest is an outside reader who needs to see one item and has no account. The share stays restricted to the address you named, and that person still reads the work.
A guest, step by step
- 01
They open your link and are asked to sign in
A share to a named address does not open for a signed-out visitor. They get a page with a sign-in that returns them to your item afterwards. For a colleague with an account, that is the whole story.
- 02
With no account, they ask for a one-time link
The same page offers Email me a one-time view link. The link goes to the address your share names, never to an address the visitor types in.
- 03
The link opens a view-only visit to that one item
It expires in fifteen minutes and works once, so a forwarded or replayed link opens nothing. They can view and download the item, and for a collection its items, and they never reach the portal around it.
- 04
They come back by asking again
Each visit starts with a fresh request, so there is no standing credential sitting in their mailbox. Removing their access ends a visit already open, immediately.
A guest suits a one-off reader, such as an auditor who needs one export. People you work with every month, such as a client team, get a sign-in through your identity provider and an external persona instead; the 800 series covers that.
Delivery is the recipient’s decision
You decide whether an email is offered. The person receiving it decides whether it arrives, and in what shape. Knowing that split stops you from misreading a quiet inbox as a broken platform.
What decides whether an email is sent
Immediate, daily digest, or off
Each person picks a delivery mode in Settings. Immediate sends one email per event. Daily collapses the day into one digest. Off drops their events.
Per category, not all or nothing
Shares, comments and feedback, and mentions toggle separately. Somebody who muted thread chatter still hears when a comment names them.
Your switch can suppress, never compel
Turning off Send an email removes the email. Leaving it on does not add one, because the recipient decides. If a colleague never got your share, ask about their delivery mode first.
Preferences follow the address
They are keyed to the email address, so a guest still has preferences and can opt out from any message. A guest who opted out and wants back in finds a Resume notification emails action on the share landing page.
A one-time link is never held back
A one-time view link is something the guest asked for by pressing a button, so it is sent at once: never deferred to a digest and never suppressed by an opt-out.
The share itself never depends on the email. Access is granted whatever happens to the message, so a notification that is muted, digested, or delayed never costs your recipient their access.
Sharing a file
Files in Resources, such as a template, a price sheet or a client’s monthly upload, are shared through the same dialog with a few differences.
Sharing a file
The same dialog
Share on a file’s page adds people or groups as Can view or Can edit, lists who already has it, and changes each row in place.
No general link
A file has no link for anyone signed in and no public link. It opens for the people and groups it is shared with.
Posting a file
Post to a channel offers Anyone who can sign in, which shares the file with every signed-in employee as viewer, or Only people with access, which posts the link and shares nothing.
Upload and share
Under Upload, Upload and share uploads one file to your own folder and opens the Share dialog on it.
Shared with me
Files other people shared with you, directly or through your persona, are listed in the Shared with me folder of Resources with who shared each one and whether you can view or edit.
Deleting a file removes its shares. An asset that loads a file gives that file the asset's audience, which the file's Used by panel flags when the asset has a link anyone can open.
Sharing from the agent session
"Share this with Dana in finance" is one request to the agent. It makes the same share the dialog makes, by the same rules, and tells you whether an email went out.
"Share the FY2025 dashboard with Jordan"
What the agent calls. This is the exchange the agent has with Plexara on your behalf, shown for the technical reader. You ask in plain language; you never type any of it.
manage_asset action list_shares asset_id 31215d803c0f4eeb982de481b95842ad -> asset_id 31215d803c0f4eeb982de481b95842ad shares [] total 0 manage_asset action share asset_id 31215d803c0f4eeb982de481b95842ad recipient [email protected] permission viewer -> share_id 570c2ca1-6856-44c6-bbb1-66a82bd39ffc shared_with [email protected] permission viewer access_mode restricted notified true message Shared with [email protected] as viewer. They have been emailed the link. It lasts until revoked.
Both calls ran against the ACME FY2025 Sales Dashboard: the read found no shares, and the share went to an analyst in the directory. A share made from the session is the same share the dialog makes: it opens only for the named person, is a viewer unless editor is asked for, has no expiry, and sends the same email under the recipient's own settings. The answer reports whether an email was sent, so the agent only says someone was told when they were. A name instead of an address is looked up in the directory, and a name that matches nobody or several people comes back with the candidates and no share. Leaving out the recipient makes a link, and a link anyone can open needs an expiry.
Ending access
Access ends the same way it was given: in the dialog, one row or one setting at a time, checked again on every request through the same governance at execution time the platform applies everywhere.
Where to look
Three places answer the questions people ask after sharing: who has this, who is waiting on me, and what was I told.
Where to look
The Share dialog
Who has this, and where has it been posted?
People with access names every person and group with their permission. General access says who else can open the link and until when. Posted to channels counts how often each post was opened.
Your Inbox
Who is waiting on me?
Access requests sit at the top of the Inbox with Approve as viewer, Approve as editor and Decline on each.
Settings, Recent notifications
What has Plexara sent me?
The subject, category, and delivery status of every notification addressed to you, newest first, beneath the preferences that govern them.
The conversation your share starts
Sharing an item puts the recipients inside its feedback threads, so your sharing decisions are also decisions about who hears about comments. The rules below are worth knowing before you share something with fifty people.
Who hears about a comment on something you shared
A comment reaches the people who can already open the item
When somebody opens a thread on your dashboard or replies to one, the notification goes to the owner, the thread’s author, and the people it is shared with. Sharing an asset is also a decision about who gets pulled into the conversation on it.
An @-mention changes the category, not the count
Type @ in a comment and the composer suggests the people who can already open the item. Anyone the comment names is notified as a mention instead of as thread activity, so one comment never sends the same person two emails.
On a widely shared item, the people named get through first
Mentions are queued ahead of the general fan-out. On an item shared with a large group, that ordering keeps a comment addressed to two people from being buried behind everyone else’s copy.
You cannot mention somebody into access
A mention may only go to somebody who could open the item anyway. Type an address for somebody without access and the composer says so while you write. Share the item with them first, then mention them.
Clients and partners
A guest suits one reader and one item. Clients and partners you work with every month need their own sign-in and a place to find what you shared with them.
Habits worth building
A few habits keep your access lists short and meaningful instead of long and full of links you no longer remember making.
Habits worth building around shares
Name people when you know the people
A share to a person or a group opens for nobody else, shows you exactly who has access, and puts your note in front of them. Reach for the general link when the audience is a room rather than a list.
Share with the team, not its members
When the audience is a persona, share with the group. The share follows the team as people join and leave, and the list stays one row long.
Keep general access at signed in
Anyone who can sign in covers almost every internal case. Anyone with the link is for a reader who cannot sign in, and it always has an end date.
Post to the channel instead of pasting a link
A post is a link you can take back from Posted to channels, with a count of how often it was opened. A pasted URL is neither.
Write the note
One sentence saying what this is and what you want from the reader is the difference between a dashboard that gets read and one that gets archived unopened.
Granting the narrowest access that does the job is the same least-privilege starting point the platform applies to connections, tools, and personas.
What 304 covers
Sharing one asset at a time is the right shape for a single dashboard or a single export. Sharing a set, where the reader should see the dashboard, the supporting report and the underlying export as one briefing, is the case for collections.
Key terms
Eight terms cover the vocabulary of sharing in Plexara: the parts of the dialog, the kinds of recipient, requests for access, the persona permission behind it all, and how each person controls their own mail.
Key Terms
- People with access
- The list in the Share dialog of everyone the item is shared with: the owner, then each person and group, each with Can view or Can edit and a menu to change or remove it.
- Group
- A persona added as a recipient. Its membership is read each time someone opens the item, so the share follows the team as people join and leave.
- Guest
- A recipient with no account, added by full email address. A guest only views, through a single-use link emailed to that address that expires in fifteen minutes.
- General access
- The setting for the item’s one general link: only people added, anyone who can sign in, or anyone with the link until a time you choose. Changing it keeps the URL.
- Posted to channels
- The list of channels an item was posted to. Each post is its own link with an open count, and Remove stops it opening.
- Request access
- What a signed-in person who cannot open an item asks for. The owner approves as viewer or editor, or declines, from the email, the Inbox, or the Share dialog.
- Sharing permission
- The Sharing checkbox in a persona’s Portal access settings. Without it, the persona’s people cannot share, post to channels, or approve requests.
- Delivery mode
- Each person’s own setting for how notifications reach them: immediate, daily digest, or off, with separate switches for shares, comments and feedback, and mentions.
