Both terms relate to streamlining logins, but they differ in scope:

• Single Sign-On (SSO): Allows a user to log in once (e.g., to a university portal) and gain access to multiple, internal applications without needing to re-enter credentials.
• Federated Access: This is a more advanced form of SSO that allows a user to log in to one domain (e.g., your university) and securely access a partner's or external organisation's application (e.g., a shared research database). Federation is essential for multi-partner access and external identity management (often using protocols like Shibboleth).

Yes, our SSO solutions fully support both Multi-Factor Authentication (MFA) and Conditional Access, which are non-negotiable for modern security:

• MFA Support: We support various MFA methods (e.g., authenticator apps, tokens) that integrate seamlessly with your existing Identity Provider (IdP), like Azure AD / Entra ID.
• Conditional Access: We enable granular Conditional Access policies that define when and how users access resources based on factors like user group, location, device health, and network security. This ensures maximum security control.

Absolutely. Granular control over user access is fundamental to our SSO and access management platform. You can control access through several integrated methods, including: 

• Role-Based Access Control (RBAC): Assigning permissions based on job function (e.g., staff vs. student).
• Attribute-Based Access Control (ABAC): Using user attributes (e.g., department or enrolment status) to grant or deny access to specific applications.
• Group Management: Syncing your existing directory groups (e.g., LDAP or Active Directory groups) to control application authorisation automatically.