Deeplinks: Access member profiles from external tools

Follow

 

Who this is for

Logged-in Dashboard staff who need to open a client profile from another tool, such as a center system that already knows the member id.

Open a profile in the current location

Use this when the staff member is already working in the location that owns the client.

  1. Sign in to the Glofox Dashboard.
  2. Open a link in this form: #/members/<memberId>
  3. The client profile opens.

Reloading the page keeps the same link and opens the profile again.

Open a profile in a specific location

Use this when the link should name the location as well as the client.

Link form: #/locations/<locationId>/members/<memberId>

  • If staff are already in that location, the profile opens and the location does not change.
  • If staff are in a different location they are allowed to access, Dashboard switches to the location in the link and then opens the profile.
  • The link stays in place across the reload that a location switch uses.

Permission

Staff need the existing permission to view clients. This release does not add a new permission.

If staff do not have that permission, the client profile does not open. After a location switch, staff who cannot view clients at the new location are sent away from the clients route.

When the profile does not open

Member problems

  • Unknown or invalid member id: the profile does not open, and staff see a warning that the member could not be found.
  • Inactive member: the profile does not open.

On a location-scoped link, a member problem after a successful switch leaves staff in the target location. They see the same member warning as the same-location link. They do not see a location error.

Location problems

If the location in the link cannot be used, staff stay on the location they were already in. The profile does not open. Tokens and the current location stay on that starting location.

Each case has its own message:

  • Staff do not have access to the location: ERROR_LOCATION_NO_ACCESS
  • The location is deactivated: ERROR_LOCATION_DEACTIVATED
  • The location id cannot be found: ERROR_LOCATION_NOT_FOUND

Final wording for these three messages is still pending. Until that copy is updated, staff may see these message keys. A single generic switch error for all three cases is not the expected result.

Not in this release

  • Staff who are logged out are not returned to the member link after they sign in.
  • Global Search is unchanged. Staff can still search for a client from the Dashboard. A link is an extra way to open a profile when the member id is already known.
Was this article helpful?
0 out of 0 found this helpful