Plexara
Working with People Outside the Company
801 - Who can open what: people, groups, guests, and one general link
The Share dialog by access. People are added with a role that changes in place, with Undo after a removal. A persona is a group whose membership is read when the item is opened, so the share follows people joining and leaving. A guest views one item and nothing else. An item has one general link, restricted to the people added, open to anyone who can sign in, or public until it expires, and changing it keeps the address, so a link already sent follows the new rule. Grounded in a collection on the ACME demo tenant shared with a supplier’s persona.
802 - Requests for access: asking, approving, and the limits on both
What a signed-in person sees when a link leads to an item they cannot open, and the request they send with an optional message. The owner approves as viewer or as editor, or declines, from the email, from Access requests at the top of the Inbox, or from the item’s Share dialog, and approving is a share, so the link they followed opens with no further step. One waiting request per person per item, three asks a day, expiry after the period an administrator sets under Admin > Settings > Access requests, and the setting that decides whether the request page names the item.
803 - Posting to a channel: Slack, Mattermost, and email as revocable links
Posting an item to a team channel from the Share dialog. A post is a link share of its own, listed under Posted to channels with how often it was opened, and Remove stops its link opening without touching any other share. The poster chooses who the link opens for, anyone who can sign in or anyone with the link until it expires, and sees a preview of what the channel will show. Files post as signed-in links only. The same post is one call for an agent or an automation, and the channels offered are the ones the person’s persona reaches.
804 - Portal permissions: the persona editor, area by area
What a persona allows in the portal, separate from what its agent may call. The persona editor groups its settings by surface: identity, an access summary the server computes from the page as it stands, the AI assistant’s tools, connections, API endpoints and instructions, and Portal access, one level per area from assets and files to catalog, automations, PDF export and earlier versions. The sharing permission takes the Share action away everywhere. Deleting a persona first lists everything that still names it.
805 - Your clients as external people
An external persona per client organization, and the people in it. Their accounts live in your identity provider, given a role that resolves to the persona, and they sign in like anyone else. Whatever the persona’s other settings say, they see only what is shared with them or their persona, as viewers, read and write only shared threads, cannot share, and have no agent access, which the platform refuses in code. The share dialog, the user directory and the audit drawer mark them External. Built on the ACME demo tenant with a supplier persona.
806 - Files from outside: uploads, External files, and a client’s file as a table
How a file gets from a client to your team. An external persona can let its people upload, and each upload lands in the uploader’s own folder, shared with no one on arrival. Staff whose persona has External files at View or Manage open every external person’s folder under External files on the Resources page. From there a client’s monthly file is registered as a table and joined to the warehouse the way the 500 series registers any spreadsheet.
807 - Capstone: a supplier’s collection, thread, and monthly file
The series end to end on the ACME demo tenant. A quote review built from the supplier’s registered price sheet and November sell-through, filed in a collection shared with the supplier’s external persona and an ACME analyst. A shared thread asks the supplier a question while an internal thread beside it stays with ACME. The supplier’s revised sheet arrives in their folder, is registered over the same table, and feeds the next review.
700 · Endpoints and Forms
Automations other systems call as lookups and feeds, and forms people fill in, with bot checks, encrypted fields, and a run for every submission.
Up nextInsights
Editorial pieces on architecture decisions, comparisons against the alternatives, and where this market is going. Read in any order.