Your feedback drives the Concourse roadmap! Review and vote for existing ideas or submit new ideas.
For immediate technical support, please follow this guidance to open a Service Now ticket.
Put simply:
Adding users one at a time creates issues with managing permissions and adding many users at a time. We should revisit our solution for adding and bulk managing permissions via the Settings page as this is a key piece of Concourse functionality.
Why it matters:
Improves usability: User should be able to add, edit, and confirm users when adding to a workspace.
Reduces user frustration: Reduce the need to add, find a user, then change their permissions.
Prevents errors: Users have a chance to review who's being added and their permissions before they're added to a workspace.
What's needed:
Review solution for adding users and for managing bulk permissions
while adding users in bulk, update the roles, permissions, access to integrations
Implement fixes in the UI to address any issues
search user in the firm (add member picker) vs search users in the workspace
import section can be brought down
Once user is added, the loader shows even after the user has been added successfully. Adds to user confusion
When we add a new users, show the newly added user at the top
Do we need roles?
When we add Other managers, the role shows Other manager for a sec and then shows roles again
In the detail section, why do we need Scope id and Project plan section
Should we allow users to edit SF id, in the settings page?
Ability to add back users to integrations if they are removed from any of the integration
In the Pursuit phase, all users should have full permission by default- Nish
If we keep the Team Members section active during workspace provisioning, how should we display users in the UI as new members are added? A user should only be considered fully added to a workspace once they have been successfully provisioned across all integrations. Refer CONC-I-2162
While searching users through Add user picker; surface colleagues with the closest org relationship at the top
Order: Same Team → Same Practice → Same Platform → Others.
use org data to infer relationships.
Ability to bulk update user roles/ permissions
Support preferable name search in addition to exact match For example, if a user searches for “Jessie”, the system should also suggest “Jessica” (and vice versa), ensuring that people can be found using the names they are most commonly known by.
Note: Work with UX to identify the key areas we need to improve
Jessica Beck
