# What are Redox organizations, users, and service accounts?
> **New release coming soon**
>
> This feature is getting some upgrades. You might see details based on the next release, so some of these changes might not exist in production just yet. Stay tuned for the release!
Think of an organization like your company’s secure office, and users as the team members you invite inside. With organizations and specific users, you can:
- Collaborate securely: Invite developers, project managers, and support staff to work together within a single, controlled space.
- Manage permissions: Control which users can access different environments (i.e., development, staging, production) and assets, as well as what actions they can perform.
- Maintain ownership: Ensure that your company’s integration assets are owned by the company itself, not tied to an individual employee’s account.
## Redox organizations
A Redox **organization** is a virtual representation of your company’s account on the Redox platform. An organization contains all the configurations and assets that enable integration with your connections.
The default **owner** of an organization is the person who creates it. However, there can be multiple owners assigned to the organization. [Learn how to create an organization](/how-to-use-redox/manage-your-redox-setup/create-or-update-a-redox-organization).
> **Deleting production organizations**
>
> Organization owners can delete duplicate or unnecessary organizations _before_ go-live. [Learn how to delete organizations](/how-to-use-redox/manage-your-redox-setup/delete-a-redox-organization).
>
> For security reasons, though, only a Redoxer can delete an organization _after_ go-live. Talk to a Redoxer if you need to delete a production-level organization.
## Users
A **user** is anyone from your company that you want to include in your Redox organization. This means they have a login to the Redox dashboard or can access your Redox organization via APIs.
Organization owners or admins can invite users to a Redox organization. [Learn how to add a user](/how-to-use-redox/manage-your-redox-setup/view-and-invite-users-to-a-redox-organization).
> **Membership limit**
>
> One user can belong to multiple organizations. There’s a limit, though—which you probably won’t hit. You’ll run into an error if you try adding a user to more than 400 organizations.
Organization owners or admins also manage which users have access to which environments. [Learn about environments](/basics/managing-access-for-your-redox-organization/what-are-environments).
## Service accounts
A **service account** is a machine user configured to perform tasks within a Redox organization. You can use these for cron jobs, scripts, and other automation tools. Some use cases might be:
- A cron job that checks for triggered alerts or VPN statuses every morning.
- An AI agent that writes or edits config modifiers for your subscriptions.
A user can grant access to a service account at their user role level or below. We recommend granting the minimum required permissions for a service account operating on your behalf within Redox.
A service account within a Redox organization is visible to all users, but only organization owners or admins can edit service account permissions.