Slate Portals have several options for authentication, depending on the intended End-User audience for the portal. Security Scopes determine what type of records can log in to any given portal. Additional restrictions can be placed on portals vi...

Dataset portals can have custom login instructions that differ from those that applicants see when they log in. Custom instructions can be useful for dataset portals when there might be different content and information to communicate. Be aware: a c...

Portals that use the Anonymous/Guest setting can be useful for displaying information to the general public as well as including links to forms and/or event registrations. However, there may be cases where users want the option to use the same por...

Each Slate database has a single branding template that determines how external-facing pages hosted in Slate will appear. This branding is controlled by the Slate  Branding Editor , which enables the editing and previewing of Slate branding w...

You can restrict who can access and edit individual portals and Express Portals by clicking Edit Permissions and then clicking Add Grantee .   These grantees can be can be individual users, or they can be all of the users with a g...

When creating a new query within a portal, a "Portal Identity" filter is automatically added. This filter is intended to limit the query results based on the record currently logged into the portal. This default filter is written in SQL , which is ...