Skip to content

Refresh from the Identity Server

Chat does not ask the Identity Server about everything on every request. It keeps a copy for a short time, so a change you make in the Identity Server can take a few minutes to show up in Chat. Refresh from Identity Server removes the wait.

These are Chat’s default times.

What How long
Who is in your workspace, their roles and what those roles mean in Chat about 5 minutes
Your workspace details, your applications and whether Chat is enabled for each about 15 minutes
People’s display names, emails and avatars about 24 hours

Two things are quicker.

  • Someone Chat last saw as having no access is checked again, at most every 30 seconds. A person you have just added to the workspace can usually get in within that time.
  • When you save a role’s Chat permissions, Chat discards its copy of everyone’s access in your workspace at once. The change reaches people within about a minute.
Chat permission: administration.manage

Without administration.manage, the button is not shown.

Administration, at the top right, next to the page title: Refresh from Identity Server. While it works, the button reads “Refreshing…”. Chat then confirms: “Identity data will be re-read from the Identity Server on the next request.”

Use it right after you change something in the Identity Server and want Chat to follow at once:

  • You assigned or removed a role for someone.
  • You added a person to the workspace or removed them.
  • You switched Chat on or off for an application.
  • You created or renamed a role or an application.
  1. Make your change in the Identity Server.

  2. In Chat, open Administration and select Refresh from Identity Server.

  3. Ask the affected person to open or reload Chat, or check the change on the Members or Applications tab.

The refresh marks everything Chat holds about your workspace as out of date: the workspace and its applications, the members and their access. Chat does not fetch it all at that moment. Each piece is read again from the Identity Server the next time a request needs it.

Display names, emails and avatars are not covered; they update on their own schedule. The refresh also does not change what any role may do in Chat. That is set on Roles and permissions.

Every refresh records IDENTITY_REFRESH_REQUESTED in the audit log. Chat re-checks your access at the Identity Server before it carries out the refresh.

Assigning roles, adding people and switching Chat on or off for an application: see the Identity Server documentation.

The same action is available through the API: Refresh from the Identity Server. These operations need a user token; a machine client never gets administration permissions.