Info |
---|
TeamForm has defined user |
...
The below Groups are to be created on the customer Identity and Access Control Provider (IACP). Once setup the access groups can mapped into TeamForm to provide synchronised access and control.
Access |
---|
Access
Functionality
Directory (typically given to all team members)
Directory Only
Directory view (for default workspace only):
View tags if set visible in Directory via tag config
Groups | Directory User | Power User | Reporting User | Admin | TeamForm Support |
---|---|---|---|---|---|
Typically given to | All team members | Leaders of teams, to enable team and work planning | Analyst / reporting, some leadership roles, admin roles | TeamForm Admins | Typically reserved for TeamForm Support |
| |||||
Directory View |
|
|
|
|
|
TeamForm App |
|
|
|
| |
TeamForm Reporting |
|
|
| ||
Admin Controls |
|
| |||
Dev Tools |
| ||||
| |||||
Directory |
|
|
|
|
|
Power (typically given to leaders of teams, to enable team and work planning)
Directory and TeamForm App
Directory plus
All from Directory Users and:
|
View other workspaces via workspace switcher in directory and TeamForm app
View & edit global settings
Workspace management
|
view people, team history
Planner/forecast/team builder/allocate people (if enabled) for their team only if user-based Group Access restrictions are enabled - see below)
Admin (Typically given to TeamForm Admins)
As above plus admin controls
| |||||
Tags |
|
|
| ||
Workspaces |
|
|
Reporting (typically analyst / reporting, some leadership roles, admin roles)
| |||||
| |||||
Planner | No access |
| |||
Forecast | |||||
Team Builder | |||||
People Allocation | |||||
Reporting | No access |
|
|
TeamForm Support
All of above plus dev tools
| |||||
Settings | No access | No access | No access |
| |
Dev Tools | No access |
|
|
|
|
User Home
A user can be shown a personalised landing page in both App & Team Directory.
...
When a user makes a request we attempt to match the email on their auth0 profile to the email addresses that we have imported. We first try an exact match, and then a lowercase match.
...
Troubleshooting
ensure the person data returned from the backend has the id attribute. The easiest way is to use
devtools
on Chrome or Firefox and inspect the person -> attributes payload on the network tab.Seek TeamForm support to ensure the user’s email on their auth0 user matches what we’ve stored in the backend. Use the auth0 web app to see the user’s email addressin TeamForm’s authentication platform (auth0) matches that loaded into TeamForm from the people or HR information system.
The feature can be tested by performing an import that has your own email address as an attribute, and then visiting Team Directory or App.
...