-
Type:
Improvement
-
Status: Resolved
-
Priority:
Medium
-
Resolution: Won't Fix
-
Affects Version/s: 1.3
-
Fix Version/s: None
-
Component/s: Administration , Backend / Domain Model
-
Labels:None
Hi folks,
Thanks for your continued support and feedback, we wanted to give you an update on the status of this issue.
Over the medium term, the direction we're taking with Crowd is to focus on scalability, reliability and performance. Unfortunately, it means that this feature is unlikely to be included in any near-term improvements to the product, as workflows and management don't align with our future direction.
We've decided to close this issue because we feel that by leaving it open, there's undue expectation that the issue is being actively worked on, and we don't want to give you the wrong information. We are aware of the issue, and recognise that it is something that needs to be done, however, it's unrealistic that it will ship within the next 18 months.
Regards,
Eugene
Atlassian Product Management
At present, the implementation of roles in Crowd is identical to the implementation of groups. Additional development work would be needed to differentiate the functionality of roles from groups.
We need to consider allowing role-based access control via Crowd.
Request to all Crowd customers and users:
- Please add a comment to this issue and let us know how you'd like to use roles.
- blocks
-
CWD-57 Security Provisioning in the Administration Console
-
- Resolved
-
