Nickelled does not handle SSO authentication of users at our end, but as no-code guide triggers and URLs are unlisted, you can protect Nickelled guides using your own SSO.

In practice, this means that no-code guides can be placed behind your SSO authentication (for example, on an intranet page or launched from within an SSO-protected app) and users will not be able to see them unless they have access to those pages.

Did this answer your question?