Auth
Overview
Appteum's Auth engine abstracts away all the complexities of a typical Auth service, giving users access to your app and allowing you to control their data access through a simple, intuitive UI.
There are two parts to every Auth system:
Authentication
Authentication is all about answering the question of who this user is and whether they should be allowed access.
You can authenticate your users using one of the following methods:
- Email & Password.
- Social providers - Coming Soon.
User Management
To create a workspace User programmatically, check out the Auth APIs.
- Create a workspace User from the Admin Dashboard:
- Edit an existing workspace User from the Admin Dashboard:
Anonymous User
The Anonymous User is a special type of user that bypasses the User Authentication, so no Sign-In is required.
This special user is directly related with the Workspace API_KEY.
You can now interact with the Object APIs by passign the x-api-key parameter only.
You can control Anonymous User access the same way as any normal workspace user, using Profiles and Permission Sets.
By default Anonymous User is assigned the System Administrator profile, but you are free to change it to your own preference.
You should treat the Anonymous User with caution, limiting access to data you are willing to expose publicly.
Authorization
Once the user is authenticated, Authorization controls what they can do.
Control a user's access using a combination of the following methods:
Profiles
Control CRUD (Create, Read, Update, Delete) and Field-Level security for each object.
In addition, profiles allow you to enable/disable system permissions.
Selecting a Profile is always required before registering a user in your workspace. See the Docs
Default Profiles
Each workspace comes with the following predefined Profiles:
- System Administrator
- Standard User
- Read Only (Editable)
Default Profiles come with pre-defined permissions.
To update the permissions based on your requirements, create a Custom Profile
Custom Profiles
Create new custom Profile by cloning an existing Profile.
Custom profiles allow you to configure the Object/Field-level permissions to your liking.
Permission Sets
You can consider permission sets as add-ons for profiles.
Create a Permission Set when you need to grant a specific group of users access to resources in addition to the access they already have through their profiles.
Unlike profiles, you can assign users to multiple permission sets.