Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.


When integrating with Maestrano, it is good practice to setup single sign on and single billing.
Here are listed the different scenarios to test in order to make sure that everything is working properly.

...

Single sign on allows your users to have a unique account for both your app and Maestrano. Please, make sure that the 6 following scenarios are validated in order to ensure a seamless experience to your users :

  1. When a user launches your application for the first time from the Maestrano dashboard on their company, it creates a new user account in your application, using the user and company details
  2. When the same user launches your application the following times from Maestrano (same user, same company, same app instance), it redirects them to the existing account already created in your application
  3. When a user launches your application from a second company on Maestrano (same user, second company), it creates a new user account in a new company in your application
  4. When a new user launches your application for the first time from an existing company, it creates a new user in an existing company in your application.
  5. When one of your existing users creates an account on Maestrano and launches your application from their dashboard, you should ask the user to be redirected to their account.
  6. When a user deletes your application on Maestrano, you should stop sending bills/invoices and stop fetching/sending data for this account to Maestrano.

...

The following scenarios, if validated, will ensure that your users will receive a unique bill for each application they use on the Maestrano platform.

  1. In case the application has a free trial, when a new user subscribes to it, no bill is pushed to Maestrano before the end of the trial period.
  2. When a user subscribes to the application with a billing plan, a recurring bill is sent to Maestrano for this organization and the user will be invoiced every month
  3. A new bill is sent to Maestrano for this organization every time the user should be invoiced
  4. When a user changes its billing plan on the application, the old recurrent bill is deleted from Maestrano and a new recurring bill is created
  5. Bill amounts are updated the month after.
  6. When the last (or unique) user of a company deletes the application on Maestrano, the recurrent bill is deleted from Maestrano
  7. No new bill is sent to Maestrano

Again, you can refer to this article: Single Billing, in case of issuestrouble.