Workspaces

A workspace is a top-level container for all your team's data and configuration in OrgFlow, and usually corresponds to your organization, or in some cases, a smaller team within your organization.

Your workspace contains:

• Your team's stacks and their contents
• Your team members and their roles (access levels)
• Invitations to onboard new team members
• Your subscription, billing configuration and billing history
• Other workspace-level settings

Everything you can do in OrgFlow takes place in the context of a workspace.

Users and members

Your workspace provides a security and access control boundary that isolates your team from other teams. This is achieved and managed through member relationships between users and workspaces, as shown below:

Users

Users and workspaces in OrgFlow are independent. A user account is personal to an individual, and used by OrgFlow to authenticate and identify that individual by means of a unique username (email address) and a password. It is created, owned and managed entirely by the individual herself - not contained in any workspace. A user account is completely free, requires only a valid email address and a name, and is not associated with any subscription or billing concerns.

Members

A user can be a member of a workspace. A member technically lives inside a workspace and represents a relationship between a user account and that workspace. Each member has a role which governs what the user can and cannot do inside the workspace. All members of a workspace have at least read-only access to everything inside the workspace; this may influence which workspaces you create, and how you name and configure them. See the section about roles and permissions to learn more.

A user can be a member of any number of workspaces, and a workspace can have any number of members.

When you sign in, if you are not already a member of at least one workspace, you are prompted to create one. The user who creates a workspaces becomes its first member.

Workspace owner

A workspace always has one member who is designated as the workspace owner. The workspace owner always has full control of the workspace. The user who creates a workspace automatically becomes its owner. The workspace owner can transfer ownership to another member if needed.

Invitations

A member in a workspace can create invitations in order to onboard new members. An invitation is created by providing a role and a recipient email address. An email with the invitation link is sent automatically to the provided address.

The email address is only a delivery vehicle

The email address provided is only used for delivery, not for identification or authentication. The invitation link can be used to accept the invitation using any OrgFlow user account with any email address.

If the recipient does not already have a user account, she can sign up for one as part of accepting the invitation. The invitation link can also be distributed to the recipient manually through some other trusted channel.

The invitation link can be used to accept the invitation and become a workspace member with the specified role.

Subscriptions and billing

Your workspace also manages your commercial relationship with us. It contains your subscription and, if applicable, your billing information and billing history.

A free subscription is automatically created with every new workspace. You do not need to provide any billing information. This free subscription includes sufficient features and resource allowances to build and operate a Salesforce DevOps workflow for a small number of environments. You may use this free subscription for as long as it meets your needs, including for production use.

As your needs grow, you may choose to upgrade to a paid subscription, which allows you to use features and resources beyond those included in the initial free subscription. When upgrading to a paid subscription, you will need to provide billing information, including your billing address and a payment method.

To learn more about our pricing plans and subscription model, see the section about billing.

The features and resource allowed by your subscription (whether free or paid) are applied across everything inside your workspace. For example, if your subscription includes five environments, those environments can be split across the stacks in your workspace as you see fit. If your subscription includes 3000 active worker minutes per month, all jobs that run (in any stack in your workspace) count against those 3000 active worker minutes.

Structuring workspaces

How you structure your workspaces in OrgFlow is up to you and depends on your needs. A single OrgFlow user account can create, own and be a member of any number of workspaces.

However, several factors may influence how many and which workspaces you choose to create:

• Access control - every member of a workspace has at least read-only access to everything inside that workspace. Use separate workspaces if you need to completely segregrate access.
• Billing - subscriptions and billing are configured at the workspace level. To segregate spending or billing between different departments or teams, you can create separate workspaces.
• Licensing terms - as per our license terms, a workspace and its subscription may only be used to support a single organization. If you use OrgFlow to support more than a single organization, you must do so with separate workspaces.

For most scenarios, a single workspace for your organization is sufficient.

If you are a larger organization with multiple independent teams that need to be separated from one another in terms of access control or billing, you may find it practical to create one workspace per team.

If you are a Salesforce consulting organization planning to use OrgFlow in your customers' Salesforce environments, you will need to create a separate workspace for each customer you support, so that your customers are isolated from one another and cannot access each other's data and configuration. This also ensures that you are compliant with our licensing terms by giving each of your customers their own OrgFlow subscription, and makes it easy to hand over ownership of the workspace to your customer.