RapidIdentity Product Guide: New UI


A RapidIdentity Connect project can be thought of as a container that holds a collection of Action Sets along with their associated data and log files, RESTPoints, and credentials. By default, there is a single project called <Main> that cannot be deleted. Additional projects can be created as needed or desired.

Projects are isolated from each other at runtime so that Action Sets and RESTPoints in one project can only reference other Action Sets and access files or use credentials from within that same project.

The primary reason for using separate projects is related to access control. Each project can be configured to use separate, per-project roles that can allow a specific set of users to only use that project, or define OAuth credentials that can be used to only access RESTPoints within a single project. Projects are also useful as a way to share, back up, stage, or migrate parts of your Connect configuration.


User-defined Action Sets will be saved in <Main> unless a different project is specified.  These Action Sets may include, but are not limited to, the creation, inclusion, removal, or disabling of various group member user accounts, various SQL queries to obtain or update data, and Action Sets to log or graph data.


As workflow increases, multiple projects will exist and it is likely that Action Set building within projects will involve overlapping characteristics, such as accessing a particular database to extract data or update directories. Duplicate, Export, and Import all allow projects and Action Sets to serve as templates. Projects can be further managed through the Connect Settings - Projects menu.