Aleria has several sharing surfaces because different kinds of work need different access. Check the sharing controls on the specific chat, project, Source, skill, agent, or app you intend to share.
Share the intended item
Open the item's sharing controls, choose the available audience, and review what recipients will be allowed to do. Where a share link is offered, copy the link after confirming its scope. Do not assume that copying the browser address creates access for someone else.
For a project chat, Private limits access to you. Sharing with the project lets current members open and continue the conversation. Use the displayed permissions rather than treating every shared view as read-only.
Resource access is separate
Sharing an agent or project does not hand another person your external account credentials. A colleague may need to enable a plugin and connect their own account before performing the same action.
Apps have their own access controls, and the data inside an app can have additional permissions. See sharing apps.
Review before and after sharing
Read the content, attachments, and generated files before making them available to others. Test access with the intended recipient, especially if the item combines project context and connected data. When access is no longer needed, remove the grant or revoke the share link where offered.
For recurring output, review automation access as well.