Admin permissions and content privacy

As an admin you run the organization. You are not a master key to everything inside it.

Being an owner or admin gives you broad control over the org. You invite and remove people, set their roles, build groups, decide what new content defaults to, and configure the workspace. The admin pages are where all of that lives.

Your admin role does not give you a way into your members’ private content. That is deliberate.

What you cannot see

If a member keeps something to themselves, you cannot open it. It does not appear in your sidebar or in your search. Promoting yourself, or anyone else, to admin changes none of that.

Three quick cases.

A member writes a private note about their own performance review. You are the org owner, and you still cannot read it.

A member shares a project with you as an editor. Now you can see it, because they shared it with you. Being an admin played no part.

Someone leaves the company. The notes they kept private stay private. Removing them from the org does not hand you their content.

What you do control

You set the starting point for new content through default permissions. If your organization wants new notes to open to everyone by default, you set that. If you want everything to start locked down, you set that instead. Members can still change the setting on their own items.

You decide who is in the org and what role they hold on the Members page. You bundle people into groups so that granting access stays simple.

Narrower admins

You can give someone power over one area without making them a full admin. A domain admin runs a single feature, like files or calendar. A files domain admin does not get to read everyone’s private files.

Chat is the one exception

Chat is the single place where moderation reaches across content. Channels are shared spaces, not personal documents. So org admins and chat domain admins can moderate across channels.

On cloud, neither can we

The same line holds for us. If you run on cloud, being a platform operator on our side does not let us into your organization’s content. The only way we see anything is a support session that you approve, scope, and revoke. The principles page covers how that works. On self hosted, there is no us to ask.

When you think you need access

Sometimes you will genuinely need to get into something a member owns. There is no admin override. Ask the owner to share it with you, or have ownership transferred to someone who should hold it. If this is about a person leaving, transfer ownership before they go.

If you want a tool where an admin can quietly read anyone’s notes, you want a different product.