🚧 The Saascannon docs are currently under construction, we are working hard to document Saascannon thoroughly 🚧
Concepts
Billables

Billables

Billables represent a single payment provider customer. They are intended to be created via an api call and the id used to save against your billable entities. Then, when a customer needs to manage the billing of a billable entity, they will just need the id in their frontend shop modal call. So long as they have access (see managing access) to the billable, they will be able to manage the billing for the billable.

Managing access

Users and billables can be linked to eachother with api calls or in the dashboard allowing you to manually or programatically manage which of your users can manage certain billables. When a user is linked to a billable they must be given a role for that link. This can either be admin which allows users to manage the billable or beneficiary which grants permissions derived from the billable plan, but not manage it.

User billables

Within the tenant shop settings page (opens in a new tab), you can toggle 'user billables' which will create a shop for each user, allowing them to directly have subscriptions. In the background, this will create a billable for each user and assign them access to it. This means that you can give access to a user's billable profile to other users if you wish.

Granting permissions

Permissions are granted via the billable's Plan's assigned roles and permissions.

If a user should get permissions from a billable, but not be able to manage it, they should be added as a beneficiary.