CONVERGE access is built from three layers: the module a user can open, the role they hold inside it, and the fine-grained permission matrix that toggles individual features. Together they decide what a user sees and can do.

The four modules

• Fairway — faculty-facing matches, opportunities, profile, inbox.
• Signal — Research Development queue, help responses, faculty enrichment.
• Drive — leadership analytics and engagement insights.
• Clubhouse — institution administration: users, data, settings.

A user is granted one or more modules. The header's module switcher shows only those they can access. Direct URLs into a module the user does not have show an access-gated page.

Roles

• Faculty — default role for Fairway users.
• RD Staff — operates Signal; can claim help requests and respond.
• Leadership — read-only analytics in Drive.
• Institution Admin — manages users, settings, and data in Clubhouse.
• Converge Admin — cross-customer platform administration. Protected from deletion or downgrade by other admins.

The role-security matrix

Beyond roles, individual features are toggled in a permission matrix managed in Clubhouse. This lets institutions, for example, allow RD staff to view but not edit faculty profiles, or restrict who can send outreach emails on a faculty member's behalf.

Acting as another customer

Converge admins can switch the customer they're "acting as" from a scope picker. All data, queries, and actions are then scoped to the chosen customer (or to a Global view that aggregates across customers for read-only insight).