Give Xelence Studio users access tokens limited to what they need
Also listed as: Scoped PATs for Xelence Studio users
What is it?
Xelence Studio users can create personal access tokens, which work like passwords for tools and scripts, and limit each token to only the tasks it is needed for.
Why does it matter?
Less exposure if a token is lost or misused, because it can only do what it was scoped to do.
Start thinking about
- Which identity provider, such as Entra ID or Okta, should staff and constituents use to sign in?
- Which of your policies, such as password, session or network rules, should Xelence enforce?
- How often do you review user roles and access, and who signs off on the review?
- How quickly can you remove access when staff change roles or leave?
- What does your policy say about using generative AI with personal or sensitive information?
- How will you fit the security changes in each release into your change and testing process?
Terms used on this card
- Access token
- A digital key or pass that proves a user or system has signed in, or is allowed to call another system.
- Xelence Studio
- The web-based design tool your developers use to configure Xelence solutions, such as forms, rules, workflows and reports. It has Git version control built in.