For Companies
A CatalogOf Your Own
Your company has a way it wants the work done: the roles, the checks, the workflows people should reuse. Put those in your own catalog, decide which groups are offered it, and let Plexon hold the repository or point at one you already own.
Related features
Two Places the Content Can Live
The first question the wizard asks is where your catalog lives. Plexon can create and hold the repository for you, which is the short path and needs nothing set up first. Or you point at a repository you already own, which keeps the content on infrastructure you control and under whatever review your team already runs. The row tells you which kind it is at a glance.
- Plexon holds it: nothing to connect, nothing to maintain
- Your own repository: your infrastructure, your review, your history
- The Plexon-held option stays greyed out until your hosting is connected and verified
- Deleting a Plexon-held catalog offers to delete the repository with it. Your own is never touched
A Version Lands as a File
Publishing is uploading a zip. The row then reads the version number, the date, and the address of the person who uploaded it, so the question "which one is live and who put it there" has an answer on the screen rather than in someone's memory. For a Plexon-held catalog the name comes out of the package itself, so it cannot drift from what is inside.
- One upload per version, with the uploader recorded
- The row shows the version, the date, and who uploaded it
- A Plexon-held catalog takes its name from the package manifest
- The display name and notes are editable without a re-upload
Who Is Offered It
A catalog is not switched on for the whole company by default. You pick the audience, and you can link it to specific groups from the group page instead. Someone who leaves that group stops being offered it on their next call.
- Set the audience on the catalog, or link it from a group
- One person can be offered several catalogs at once
- Removing a link takes effect on the next call, not the next sign-in
- The people who are offered nothing see nothing, not an empty tab
Credentials You Can Check and Rotate
A catalog in your own repository needs a credential to read it, and a credential that quietly stops working is the failure this page is built to prevent. The row carries a health indicator, a Check button that asks right now, and a rotate that replaces it without recreating the catalog.
- Health shown on the row, not discovered when someone reports a broken install
- Check asks the provider immediately and reports what it said
- Rotate replaces the credential in place
- Only the catalogs in your own repository carry this. A Plexon-held one has nothing to rotate
What a Company Catalog Gives You
Your Catalog, Your Rules
The skills, agents, personas and workflows your company standardised on, offered to your people from inside the app.
Hosted or Your Own
Let Plexon hold the repository, or point at one you already own and keep the content on your side.
Versions With Names On
Every upload records its number, its date, and who did it, so nobody has to reconstruct which version is live.
Offered, Not Forced
Pick the groups a catalog reaches. Someone who leaves that group stops seeing it on their next call.
Connects to
Nothing here works alone. See the whole map for how the pieces fit together.
What feeds it
Marketplace Developer Mode authors this.
The same wizard that builds a personal marketplace builds a company one.
Personas is distributed by this.
A company ships its own roles to its people through its own catalog.
Company Admin Panel requires this.
A catalog is offered to the groups a company admin picks, so the groups have to exist first.
Where it goes
This is distributed by Unified Marketplace.
A company's own catalog sits in the same Browse dialog as every other source.