Account and developer tools
Manage team access and roles
BNex team access is scoped to a business workspace, and a member’s role and current permissions determine which workspace actions they can perform.
Updated 2026-10-12
Workspace membership
Each business operates inside a workspace. Joining a workspace gives you access to the data and tools allowed by your membership and role; it does not grant access to other organizations.
Workspace owners manage membership and sensitive business operations. Admins may manage some workspace settings and integrations. Other roles have access according to the permissions assigned to them.
Request or grant access
- Ask the workspace owner to invite you. Provide the email address you use for BNex and confirm which workspace you need to join.
- Accept the invitation and sign in. Complete the invitation flow using the intended account so your membership is attached to the correct identity.
- Confirm the required role. Tell the owner which tasks you need to perform. Request the least access that lets you do that work.
- Review access when responsibilities change. Ask an owner or administrator to update or remove membership promptly when a teammate changes role or leaves.
Sensitive actions and connected tools
- Finance and workspace configuration can require an owner or administrator permission.
- Personal MCP agent tokens are managed by workspace Owners and Admins; sending scopes are currently unavailable in the BNex token form.
- Removing a member or changing their access affects the capabilities available to connected MCP grants on subsequent calls.
Frequently asked questions
Can a workspace member see another organization’s data?
No. BNex workspace access is tenant-scoped. Membership in one workspace does not authorize access to another workspace’s records.
Who can manage MCP agent tokens?
Workspace Owners and Admins can create and manage personal agent connections in Advanced Settings. Every tool call still checks current membership and permissions.