Org & Permissions · All plans
Visibility that mirrors how your company actually works.
Teams with hierarchy and leads. People with managers, reportees and mentors. Three visibility modes for every project, task and objective — on top of the permissions Bren mirrors from Slack, Jira, Google and the rest.
Mentor link: Mei ↔ Jordan (not reporting). Imported from Slack user groups.
The problem
Either everyone sees everything, or nobody sees anything useful.
Most "AI for the company" tools have one permission model: whatever the admin connected, everyone can query. Security says no, HR says no, and the rollout stalls. The alternative — lock it all down — makes the tool useless.
Bren's answer: nobody sees anything in Bren they could not already see in the tool it came from, and every project has a visibility setting that matches how teams really share work.
How Bren does it
Structure first. Then two layers of permissions.
Teams and people
Every team has one parent and any number of children, and one lead. People have managers and reportees, and optional mentor links (senior, but not reporting). Import from Slack or Teams groups, Google or Microsoft directory, CSV, or SCIM on Enterprise. Edit in a drag-and-drop tree.
Layer 1: mirrored from source tools
Private Slack channels, restricted Jira projects, unshared docs: if you cannot see it there, you cannot see it in Bren. Re-checked on every sync, at most 15 minutes lag.
Layer 2: Participatory, Public, Selective
Participatory (default): owners, participants and their reporting managers. Public: the whole company. Selective: Participatory plus people or teams you add. Marking something Public disables the Selective picker.
Insights about people, deliberately narrow
Managers see direct and indirect reportees. Peers see availability and shared-project contributions only. Org admins can tighten defaults, never loosen them. Private notes are outside all of this.
Who it is for
Who says yes because of it
IT and Security
Least-privilege scopes, mirrored permissions, SSO on Business, SCIM and audit logs on Enterprise.
HR and People
No surveillance; no peer-to-peer performance visibility; private notes private.
Team leads
Default team visibility into your own work, without asking an admin for every project.
FAQ
Org & Permissions: the details
What does each team see by default?
Every team sees its own owned and participatory entities unless a project is specifically marked private in the source tool.
Who can see an OKR?
Participatory by default: the owner, the owners and participants of tasks feeding into the KR (up to one level down) and their managers. Public and Selective work as for projects.
What about mentors?
Mentor links are informational (senior but not reporting). They grant no additional visibility unless the mentee marks something Selective and adds the mentor.
How do reorgs work?
Edit the team tree; history follows the people; digests adjust from the next cycle. SCIM-driven reorgs on Enterprise apply automatically.
Which plans include Org & Permissions?
All plans. SAML SSO is on Business and Enterprise; SCIM and audit logs are Enterprise.
Related
Works with
Roll out company-wide without a visibility audit.
Import your org in the 14-day trial. No card. Security overview available on request.