Here is a brief explanation of how Forms for Salesforce subscriptions work.
Formstack requires a separate subscription for each Salesforce Production org. This is because our app is a Native application and is managed and provisioned using Salesforce tools. Here are some common terms you may run into.
Production Org
This is the customer's Production org on which they pay their Salesforce subscription bill.
Formstack Subscription
A Formstack Subscription is what you pay for. It represents a single SKU which is 1 Product or 1 Platform Product (which is a bundle of products). We can put a single Forms For Salesforce product on a subscription. This means that if you have multiple Production orgs, they will require a separate subscription for each.
Seats
This represents the number of people in your organization using the Forms for Salesforce product on a single subscription.
Examples
- If a customer purchases a subscription with a single seat, this means that only 1 person can use the Forms for Salesforce app on the Production org or any related sandbox org.
-
If a customer purchases a subscription with 2 seats, this means that 2 people can use the Forms for Salesforce app on the Production org or any related sandbox org.
We do not differentiate between Production users or Sandbox users. Seats represent people using the product regardless of the org. We provision the same number of users on a Production org and all of it's related sandbox orgs.
🔺 Customers can assign their users within the app in each of their orgs using the self-service Admin Settings. Our Terms of Usage require that a seat is purchased for each person using the product even if some people will only use the product in sandboxes.
Builder Users
Builder Users and Seats are synonymous and represent the number of people using the product. See above (Seats) for a more detailed description.
Users
Seats (see above) refers to Forms for Salesforce licenses, whereas we may mention Salesforce Users to reference Salesforce user accounts in an org.
We may use Users occasionally when interacting with you so please clarify which of these is being referred to so the conversation is clear:
- Seats (people on the subscription) or
- Native Salesforce User accounts on your individual orgs (usually related to access issues or SF permission sets when working with our support team)
Licenses
“License” is often used interchangeably with Subscription, Users and Seats. Please review the section above about Seats first.
We may use "Licenses" occasionally when interacting with you as well so please clarify which of these is being referred to so the conversation is clear:
- Subscription (what is paid for) or
- Seats (people on the subscription) or
- Native Salesforce User accounts on your individual orgs (usually related to access issues or SF permission sets when working with our support team)
Multiple Production Orgs
Some organizations use multiple Production orgs and maintain separate subscriptions with Salesforce for these. We can accommodate these but it is important to let us know this is the case so we can make sure that your orgs are correctly provisioned to avoid future downtime or billing issues.