Authic provides the option of creating Plans for your users to join when they sign up for your application. If you configure one or more Plans for your application, your users will be prompted to join a plan when they first sign up.
Your users can see and change their plan membership by visiting their Authic hosted, account edit screen.
Once you have created your Authic Client application, you have the option to create Plans for your users. To create a Plan, visit the Plans tab on the Client Application edit screen and click on the + button in the top right of the Plans tab.
If you have created/selected a Payment Provider (e.g. Braintree) for your application, you will be able to create Plans based on plans/subcriptions configured at your Payment Provider.
If you are following good practices, you will have a number of different environments in which you run you application. For example, you might have a development environment running on your local development machine, a staging environment to deploy freshly minted code for testing and a production environment where you run your application with live users.
When you have multiple environments like this, you will need multiple Authic Client Applications configured, one for each environment. To simplify configuration, Plans can be shared across multiple Client Applications. Once configured for one application, they can be added to your other applications.
To add a previously created plan to your application, select the application from the 'Add plans...' field in the top right of the Plans tab. You will be able to choose to add any of the selected application's plans to your current application.
If you would like your users to automatically join a certain plan when they first sign up, you can nominate a plan to be the Default plan for your application.
Once set, your user will not be prompted to join the plan, instead they will be made a member automatically. If the plan is a paid plan, then they will be prompted to enter payment details to continue.
An example use case for Default plans is if your application is to have a single paid plan. Make this plan the default plan and your user will join automatically and be prompted to enter payment.
Another example is if you want all users to start out on free plans. Make your free plan the default plan and your users will join the plan. Later you can prompt them to upgrade to access other features.
You can mark a plan as open to new members. This means a plan can be joined by users that are not currently plan members. If the plan is not open (i.e. closed), then users that are not currently members of the plan, cannot become members.
You might want to close a plan to new members if you no longer want users to join that plan. For example, you might have a promotial plan that was available during beta, but should not allow new members to join.
You can mark a plan as visible. This means a plan will be visible on the select a plan screen that users are directed to when signing up, or modifying their plan membership.
If the plan is not visible (i.e. hidden) it will not be visible on the select a plan page. This can be useful when you want to create a plan that should only be accessible to people given a link with the hidden plan's code embedded in the URL. An example use case would be sending out a promotional links to a mailing list. People with the link will be able to join the promotional plan, users signing up to your application via other means will not know of the promotions existance.
To construct a link to a hidden plan is easy. Simply make a link to:
Where [subdomain] is your applications Authic subdomain and [PLANCODE] is the identifier code that you gave your plan.