Sign-In Visibility: Two-Factor Policy and Setup Status
Compare the account's two-factor requirement and session limits with one user's pending enrollment, and see the authenticator app and pass key options.
1:09 · Shown on synthetic test data.
Full transcript
Sign-in protection needs a clear policy and a clear setup status. Rebrand RCM separates the account rules from each person's security settings, so both sides can be reviewed. The sign-in security page brings two-factor requirements and session limits together. In this demo account, the displayed HIPAA mode requires two-factor sign-in for every listed role. The role controls show required. The current settings show 15 minutes of idle time and an 8-hour maximum session. These limits sit together, giving the account administrator one view of the sign-in policy. Personal enrollment is separate. Under security and two-factor, this demo user currently has two-factor authentication off and no pass keys. The visible status shows that this person's setup is still pending. The page offers an authenticator app or a pass key as the second factor. A pass key uses the device's own unlock or a security key. The options appear alongside the actual enrollment status. The value is a clearer security rollout. Review what the account requires and what each person still needs to set up. See how Rebrand RCM could support your practice's sign-in workflow.
