Security Features
Setting up users, roles, privileges and related considerations
Setting up users, roles, privileges and related considerations
Building a number of applications to form a CRM system
Security features - users, roles and privileges. Policies and procedures
Adding, viewing and removing users
How AI and No Code work together in Agilebase
Allowing access to people outside the organisation
Policies and further information
Organising users into groups for better management
The different types of privilege and how they can be assigned
Allowing users to export data to spreadsheet
Viewing, querying and reporting on log data
Viewing usage statistics relating to users, tables and views
Building, assembling and managing the whole system
Validating logins from a third party app
Customising how the user navigates an application
Options relevant to storing commerically sensitive or personal data
How to change a field from one type to another
Enforcing the correctness of data entered into the system
Options which alter table behaviour
Running a workflow whenever a record is added
Some examples of useful calculations for each type of field (text, number etc.)
Assigning table privileges
Shows which users are viewing data from this table
Helping people who have problems logging in
Using a test server to dry-run integrations
Sending data to an external tool via a database link
Resources typically useful in the later stages of development
Some interesting solutions for common problems encountered when building apps with Agilebase
These settings apply to the whole Agilebase account
Each workflow can perform a single specific action
Common patterns, or recipes for accomplishing useful tasks
Working with big data and complex views
A worked example to send Agilebase data to a third party text messaging service using Zapier
A more complex API example showing a real world integration consisting of multiple steps
Allows comments posted in Agilebase to be shared as Slack/Teams/Google etc. notifications
Logging in as a user
Creating a user account in a multi-tenanted system with an API request