The things you create in Aleria, such as sources, agents, skills, and apps, are private by default. Only you can see them until you choose to share. This keeps your work secure and keeps half-finished resources out of the workspace until they are ready.
Everything you create — sources, agents, skills, and apps — is private to you until you explicitly share it. Sharing is always a deliberate action, never automatic.
Private by default
When you create something, it is visible only to you at first. This is true for:
- Sources: databases, file collections, and connected systems you add
- Agents: the specialists you build or save from a chat
- Skills: capabilities you create for your own use
- Apps: tools you build and deploy
Private resources appear in your personal library. You can use them in your own chats and workflows, but teammates cannot see or use them until you share them.
Share with your workspace
When something is ready for the team, you can share it with the whole workspace.
- Open the source, agent, skill, or app.
- Open its Share control.
- Choose to share it with your workspace.
Once shared, it appears in the workspace library, and members can use it. (For apps, the visibility choice is "Only you" or "Your workspace." See Apps.)
Examples of when to share
- You built a skill that quotes rates the way your team does. Share it so everyone in Sales can use it.
- You created a source that pulls the latest pipeline data. Share it so boards and workflows across the workspace can read it.
- You tuned an agent for contract review. Share it so Legal has the same specialist on day one.
Share with a public link
For things that need to be seen outside the workspace, you can create a public link. Anyone with the link can preview the resource and copy it into their own workspace.
- Open the source, agent, or skill.
- Open its Share control.
- Create a public link.
- Set options such as an expiry, if available.
- Copy the link and send it.
Public links are read-only. Recipients cannot change your copy. They can only view it and duplicate it into their own workspace.
Manage access
Administrators can:
- See which resources are private and which are shared
- Revoke a public link
- Set workspace policies for what can be shared externally
A note on what sharing does and does not change
Sharing a source or agent does not bypass permissions. People still only see the underlying data they are allowed to see, and connectors still respect the access of the account that connected them. See Connectors and Deployment and security.
Best practices
- Keep resources private while you are still testing them.
- Share skills and agents as soon as they reflect your team's real process, so teammates do not rebuild them.
- Share sources when other people need them for boards, workflows, or their own chats.
- Use public links sparingly, and only for resources that do not contain sensitive data.