Access control
Team access management that stays secure as your platform grows
Organize resources into projects, reuse team permissions, connect organization SSO, and keep a clear record of every platform action.
Wodby gives teams a practical access model for platform operations. Instead of assigning permissions one user at a time, you can structure work around projects, teams, and identity providers, share resources intentionally, and keep audit trails that explain what changed and why.
Organize platform resources in projects that match the business
Applications, databases, clusters, stacks, and integrations are easier to manage when they live inside clear boundaries.
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.
Reuse team permissions instead of assigning users one by one
Team-based access models reduce admin work and make permission changes more predictable.
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.
Connect organization SSO providers for centralized sign-in
Single sign-on keeps platform access closer to the identity systems your organization already trusts.
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.
Supported providers
Use OIDC, SAML 2.0, Google Workspace, or GitHub Organization providers for organization sign-in.
Verified domains
Require verified email domains for providers that need domain-based access control.
JIT provisioning
Let eligible users create organization access through SSO when your onboarding model allows it.
Clear provider selection
Keep organization SSO distinct from regular Google or GitHub sign-in buttons.
Audit platform activity with a task history that explains what happened
Every infrastructure action is easier to review when the platform keeps a traceable history.
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.
Detailed logs
Review the context behind failed or successful infrastructure actions instead of guessing what happened.
Infrastructure transparency
See auto-scaling, failovers, and maintenance operations that happen behind the scenes.
Deployment tracking
Connect releases to the people and events that triggered them.
Governance support
Use recorded history for operational reviews, security checks, and incident analysis.
Handle onboarding, offboarding, and resource sharing with less friction
Operational hygiene matters as much as the initial permission model.
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.
Move toward more granular role control when you need it
Some organizations need stronger least-privilege rules than a broad team model can provide.
Wodby already supports predefined roles at the organization and team level, and more granular permission controls are planned for teams that need custom role definitions. That creates a path from simple access management to tighter governance without rebuilding the workflow later.
Related resource sharing is also part of that model. Teams can reuse shared stacks, databases, and clusters more intentionally when roles stay clear.
Next step
Give teams access without losing operational control
Structure platform permissions in a way that supports collaboration, reduces admin overhead, and keeps ownership clear as more teams start shipping on Wodby.