Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarifying information regarding SSO experience #269

Merged
merged 2 commits into from
Aug 22, 2024
Merged

Clarifying information regarding SSO experience #269

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
109e92d
Clarifying information regarding SSO experience
jayk-u Aug 5, 2024
fbdacd3
updated screenshot and added contextual elements
jayk-u Aug 22, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 6 additions & 0 deletions src/_help/organizations/organization-access-management.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,3 +48,9 @@ The configuration step for your identity provider depends on the specific provid
> By default, all users who get access to Bump.sh via the configured SSO will have the “Viewer” Role/Permission.
{: .info}

### Operation with Bump.sh

Once the SSO connection(s) are set up, your private documentation or hubs will only be accessible to authenticated users. You will find the link to the SSO login page in the settings of your organization.
This SSO login link redirects to the dashboard.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Maybe mention that user is redirected to private Hub or Api when it was the expected page before authentication?

And we should advice here to share url of private Api or Hub for guests, if you don't want these users to access dashboard


The login page will be displayed each time an unauthenticated user attempts to access a private documentation or hub.
Loading