Team access management that stays secure as your platform grows

Wodby projects let you group resources around clients, business units, products, or environments. That makes ownership easier to see and gives teams a more natural place to work than one flat list of everything in the platform.

Shared resources can still be reused across projects when needed, but the default structure stays easier to navigate and govern.

Create teams for developers, QA, client stakeholders, or operations, then apply those teams across multiple projects. This keeps access rules consistent and cuts down the operational cost of onboarding new people or shifting responsibilities between teams.

• Grant access to a whole team instead of repeating the same user setup.
• Delegate team membership management through team leadership roles.
• Keep permission changes consistent across related projects.

Wodby supports organization-level SSO providers so users can sign in through approved identity systems instead of relying only on personal accounts. Teams can connect common enterprise providers, verify the domains allowed to use them, and keep onboarding tied to organization access rules.

Organization SSO is included with paid plans. On the free Developer plan, teams can prepare provider settings and verify domains, then upgrade when they are ready to enable SSO sign-in.

• Start with read-only OAuth scopes for assessment and troubleshooting. Add only the permissions needed for an approved job.
• Choose the organization during authorization. Your Wodby permissions still determine which projects and resources are accessible.
• Review credential expiration and revoke access from User settings > API keys when a connection is no longer needed.

Permissions and approval are different. Agree on the changes before execution, with separate approval for production cutover or destructive operations. A tool confirmation argument is not independent proof that a person reviewed the change.

OAuth scopes apply to OAuth connections. An ordinary API key uses its owner's access without those scope restrictions. Revoking a credential stops subsequent authenticated requests; it does not undo changes or necessarily cancel tasks already running.

Wodby records platform operations as tasks with logs, timestamps, and outcomes. That gives teams a reliable place to check deployments, scaling activity, maintenance jobs, and configuration changes when they need to troubleshoot or review how something changed.

Use the MCP label and MCP-only filter to find tasks initiated through an agent connection. Details can include the authorizing user, credential, initiating tool, and client name and version when supplied. Client labels are self-reported, not verified model identities. Task history covers task-backed actions, not every read or the agent's complete conversation.

Adding new people to an existing team grants the right level of access faster, and removing them revokes it in one place. Wodby also lets teams share common resources across projects when reuse matters, without losing visibility into who can see or operate them.

• Reduce the risk of forgotten access during team changes.
• Share common resources across projects without duplicating them.
• Keep ownership visible even when multiple teams rely on the same platform components.