Entity Settings
Below is the full list of settings found on any given Entity. This is the expanded view, which is available when toggling the slider in the top right. Below the image are explanations of every setting.
deploy live: Submits all new entity and field changes, so they are rendered in the application.
backup: ???
delete: Removes the entity entirely. Record data is not lost from this action.
bulk update: ???
General
Active: Determines whether or not records from the entity is available in the application. It is often useful to deactivate unused entities instead of deleting them, in case you need to look at what once was.
System name: What the entity is called in the database and is sometimes used in configurations where a specific entity needs to be pointed out. This never changes.
Display name: What the entity is called from the point of view of the user, and can be changed at any point if needed. Below is what the plural name of the entity should be for the purposes of list views.
Description: Has no function. Is merely a reminder in the designer of what the entity is.
Icon/image: Choose an icon to display next to the entity selection in the application navigation menu. The button Icon-selector below helps with this. Example: 
edit instructions, header and script: Advanced menu to insert custom css and JavaScript to adjust the appearance and behaviour of the records.
Workflow
Initial status: ???
Deleted status: ???
Recursive delete/hide (parent trigger): ???
Satelite data synchronization: ???
Functionality
Check for Duplicates using unique key(s): This feature prevents any record from being created if another records shares its combination of unique field values. Will also prevent one record from being edited to be the same as another. This only works if at least one field is required to be unique.
Measure time spent editing / viewing each item: ???
Allow Internationalization: ???
Offline enabled: ???
Use Revision log to build log of all changes: Creates a log of all future changes to the records. Includes when and by whom the changes were made.
Use Access log to register user access to each item: ???
Use Status log to register time in each status: ???
Use Activity monitoring (historical data): ???
All users can display logs (Analyst role not required): ???
Monitor and analyse waiting time: ???
Behaviour