Tiers and privacy
Who can see a value: public, published, shared, private. The outsider view and the audit log.
In short
- Visibility is set per value, not per company: you can show your structure and keep your methods private.
- Everything an agent uploads starts
private. Only the workspace owner can publish. - An API key sees what its owner sees. Ask for the outsider view with
public_onlyon get_company_atlas.
Visibility
Visibility is set per value, not per company. A client can show their structure and hide their methods. Only the owner can publish.
- Tier
- Who can see a value.publicFound by research from public sources. Anyone with access to the profile sees it; the client can flag it as wrong.publishedClient data the owner chose to publish. Anyone with access to the profile sees it.sharedClient data shared with named people and the owner.privateClient data, the default. The client workspace and their consultant only.
- Outsider view
- A preview of a company as a competitor sees it: public and published values only. When a private value differs from the public one, outsiders see the public value and the client sees the difference highlighted.
- Audit log
- Every access to private data and every visibility change, visible to the owner.
What never to upload
Secrets (keys, passwords, tokens, connection strings), personal data about named people, and customer or financial records. Upload structure: “we invoice monthly in Stripe”, not an invoice.