> ## Documentation Index
> Fetch the complete documentation index at: https://docs.tess.im/llms.txt
> Use this file to discover all available pages before exploring further.
# Visibility
Visibility defines the privacy level of the agent created in Agent Studio. You can choose between the following levels:
Available only to members of your workspace. This is the ideal mode to keep control of internal agents.
Visible to the creator and, when workspace policy allows, to roles with **governance permissions** to audit other members’ private agents — workspace membership alone does not grant access to someone else’s private agent.
Available for use by the entire Tess user community and is listed in the Marketplace.
It doesn’t appear in the Marketplace, but anyone in Tess who receives the link can access it.
### **Why is it important?**
* Security and confidentiality: agents with sensitive data should be private or limited to the workspace.
* Controlled sharing: experimental agents can be unlisted, accessible only via link.
* Distribution and community: mature agents can be made public and shared with the entire Tess user base.
### Understanding Visibility Levels in detail
All workspace members can access the agent. It’s great for agents created by company members so other colleagues can use them.
By default, only the creator sees the agent in listings. To **audit or access** another member’s **private** agent, the workspace must grant **explicit governance permissions** (being Owner alone does not automatically unlock others’ private agents). Use for drafts, tests, or personal agents.
In this case, any Tess user can find and use the agent, and it becomes available and listed in the Marketplace. Used for agents ready to be reused by others (more generic and broad), market templates, showcases, etc.
It can’t be found in the Marketplace, and only people with the direct link can open it. It’s used when you want to share with specific clients, partners, or in beta phases for testing by other people.
### **Governance and private content in the workspace**
Visibility (public, workspace, private, unlisted) is not the only control. For **other members’ private agents and private results** in the same workspace, Tess applies an explicit **governance** model:
* **Same rules everywhere:** Agent Studio, chat, usage history, linked documents, and **external template/execution APIs** share the same authorization rules. There is no API-side shortcut that exposes another user’s private assets without the right permission.
* **No role bypass:** Being Owner or admin **does not by itself** replace governance permission to **read or audit** others’ private agents and **private sessions/results** when policy requires explicit grants — unauthorized access is clearly denied.
* **Clear denial UX:** Unauthorized attempts surface the **private content** experience (access denied) instead of ambiguous “not found” behavior.
* **Usage history:** Items you can’t open show as **restricted**, without misleading clickable links.
Who may audit private content and under what terms depends on **workspace permissions** and **governance features** for your plan (often in **Enterprise** scenarios). See also [Members and permissions](/en/members-permissions).
### **How to adjust an agent’s visibility**
When creating the Agent, you can set visibility inside Agent Studio by selecting your preferred option. The agent will be created with that setting.
In addition, you can always adjust the visibility level in Agent Studio:
1. Open Agent Studio
2. Find the agent you want to configure. You can use the search field, type, visibility, or Owner.
3. Check the Visibility column and choose the desired level
**IMPORTANT**\
\
If you choose to make your agent public, review its name, description, and content before exposing it in the Marketplace. Our team will review and test your agent before making it definitively public. If it’s rejected, they will point out the reasons for adjustment and a new review.
### Detailed Agent information (to make it public)
To access it, just hover next to the status and click the pencil.
This will take you to the agent’s detailed settings:
**Best practices**
* Start with the agent as Private during the testing phase.
* When it’s mature, switch to Workspace so the whole team can use it.
* Only make Public what you truly want to share with the community, without sensitive data.
* Use Unlisted for pilots with selected clients, without exposing it in the Marketplace.