My Organization
Overview
An organization is a secure space provided to a set of Control Hub users.
All engines, pipelines, jobs, and other objects added by any user in the organization belong to that organization. You log in to Control Hub as a member of an organization and can only access data that belongs to that organization. The specific organization data that you can access depends on the roles and permissions assigned to your account.
When you are a member of multiple organizations, you select the organization to use when you log in. After logging in, you can switch organizations. You can also choose to leave an organization.
A user with the Organization Administrator role can review and configure organization properties. An organization administrator can also enable the organization to use SAML authentication.
Control Hub sets usage limits on organizations with a Free or Professional account. For all organizations, Control Hub sets default system limits on the number of objects that can exist for the organization.
Multiple Organizations
A single user account can belong to multiple organizations.
For example, let's say that you sign up as a new user of StreamSets DataOps Platform. StreamSets creates a Control Hub organization using the company or organization name that you enter, and creates a user account using your email address. A colleague also signs up as a new user, and invites you to join her organization using your same email address. When you join your colleague's organization, StreamSets adds you as a member of that organization using your existing user account.
When you are a member of multiple organizations, you use a single set of credentials to log in to StreamSets. During the login, you select the organization to use for that session. For that session, you can only access data belonging to the selected organization.
To access data belonging to a different organization, you must switch organizations.
Switching Organizations
When you are a member of multiple organizations, you select the organization to use when you log in. After logging in, you can switch organizations.
-
In the top right toolbar, click the My Account icon:
.
- Click Switch Organization.
- Log in to your account again, selecting the other organization that you want to use.
Leaving an Organization
If you are not the organization administrator who created the organization, you can choose to leave the organization. Leaving the organization deletes your user account in that organization.
-
In the top right toolbar, click the My Account icon
(
), and then click your user name.
- On the Account Settings tab, click Leave Organization.
- Click OK to confirm that you want to leave the organization.
Configuring Organization Properties
A user with the Organization Administrator role can review and configure organization properties.
Usage Limits
Control Hub sets usage limits on organizations with a Free or Professional account. Organizations with an Enterprise account have no usage limits.
Usage Limits for Free Accounts
Object | Usage Limit |
---|---|
Active jobs | 2 |
Published pipelines (pipelines that have at least one commit) |
10 |
Users | 2 |
To increase the usage limits, view our pricing page to learn about upgrading to a paid account.
Usage Limits for Professional Accounts
Object | Usage Limit |
---|---|
Active jobs | 5 |
Published pipelines (pipelines that have at least one commit) |
50 |
Users | 5 |
To increase the usage limits, view our pricing page to learn about upgrading to an Enterprise account.
Organization Default System Limits
Control Hub sets default system limits on the number of objects that can exist in each organization. The limits protect the system from run-away scripts or unintended automation usage.
These limits are sufficient for most organizations. If you hit these system limits and have a paid account, contact the StreamSets Support team to discuss increasing the limits.
System limits cannot be increased for Free accounts.
The following table lists the default system limits within Control Hub:
Object | System Limit |
---|---|
API credentials per user | 10 |
Deployments | 50 |
Engines | 20 |
Environments | 50 |
Jobs | 500 |
Legacy Kubernetes deployments | 50 |
Legacy Kubernetes Provisioning Agents | 20 |
Pipelines (including both draft and published pipelines) |
1,000 |
Pipeline versions or commits | 3,000 |
Scheduled tasks running concurrently | 100 |
Subscriptions | 100 |
Topologies (including both draft and published topologies) |
50 |
Topology versions or commits | 500 |