Hi guys! I would like your opinion on
Hi guys! I would like your opinion on the best approach to take with Autumn based on my situation:
My app provides billing per user. Depending on the plan, a user can have a certain number of organizations.
Each organization can have a certain number of guests, but this depends on the user's plan
practical example:
Free plan
organizations :1
guests per organization: 3
Plus plan
organizations :3
guests per organization: 5
After doing some testing and reading the documentation, I am trying to figure out how to keep track of the number of users per organization. At the moment, the best solution I have found is to create a new entity for each organization and attach it the Organization plan, which has a guest count feature. From there, I can easily manage them.
However, I was wondering if this was the best approach, namely:
- having plans per user
- having plans per organization to associate with entities (always free in my case)
One limitation I have found with this approach is when upgrading plans: let's say a user upgrades from the PLUS plan to a Premium plan where there are 10 guests per organization. Would I then have to update each entity with the relevant Organization Premium plan by making a separate call for each entity? At the moment, it does not seem possible to upgrade multiple entities in a single call.
My app provides billing per user. Depending on the plan, a user can have a certain number of organizations.
Each organization can have a certain number of guests, but this depends on the user's plan
practical example:
Free plan
organizations :1
guests per organization: 3
Plus plan
organizations :3
guests per organization: 5
After doing some testing and reading the documentation, I am trying to figure out how to keep track of the number of users per organization. At the moment, the best solution I have found is to create a new entity for each organization and attach it the Organization plan, which has a guest count feature. From there, I can easily manage them.
However, I was wondering if this was the best approach, namely:
- having plans per user
- having plans per organization to associate with entities (always free in my case)
One limitation I have found with this approach is when upgrading plans: let's say a user upgrades from the PLUS plan to a Premium plan where there are 10 guests per organization. Would I then have to update each entity with the relevant Organization Premium plan by making a separate call for each entity? At the moment, it does not seem possible to upgrade multiple entities in a single call.
