...
After I setup my organization, I realize I made some mistakes and want to change pretty much everything including the legal name, name, description, primary e-mail address, founded date, primary phone number, and primary address.
After I setup my organization, I realize I should have used a different domain and want to start over or swap out to a different domain. If I can’t change domains, then I need the existing organization to be deleted so that no one can mistakenly use it
After I setup my first account, I realize I made some mistakes and want to change pretty much everything including the name, primary phone number, and primary address
After I setup my user ID, I realize I made some mistakes and want to change pretty much everything including the first name, middle name, last name, and how I want to contribute.
After I setup my user details so that I can contribute content, I realize I made some mistakes and want to change pretty much everything including my name prefix, suffix, middle initial, phone number, address, social accounts., languages, and membership in groups, teams, and initiatives.
Requirements
Requirement | User Story | Importance | Jira Issue | Comments |
|---|
Organizations | Reference to the GRCschema definition |
Ability to create and setup a new Organization with all required information as identified in the standardized account definition | Includes: legal name, name, description, domain, phone number, email address, founded year, phone number, address, social address, and classifications (e.g., NAICS Code, SIC Code …) | |||
Ability to update an existing |
Organization for all relevant information identified in the standardized account definition | Same as above | |||
Ability to upload and change the Organization logo | ||||
Ability to delete of an Organization | If users can’t delete on their own, it is fine if UC deletes on their behalf | |||
Accounts | Reference to the GRCschema definition => GRCschema - Account | |||
Ability to create and setup a new Account with all required information as identified in the standardized account definition | Includes: name, phone number, and address | |||
Ability to update an existing Account for all relevant information identified in the standardized account definition | ||||
Ability to upload and change the Account logo | ||||
Ability to delete of an Account | If users can’t delete on their own, it is fine if UC deletes on their behalf | |||
Ability to invite additional users to an account | ||||
Ability to deactivate users assigned to an account | ||||
Ability to delete users from an account | If users can’t delete on their own, it is fine if UC deletes on their behalf | |||
Ability to create, update, update, and delete Groups and add/remove users to those Groups | ||||
Ability to create, update, update, and delete Teams and add/remove users to those Teams | ||||
Ability to create, update, update, and delete Initiatives and add/remove users to those Initiatives | ||||
Register for mapper and gain access to profile and email | ||||
RBAC for at least admins vs others | ||||
Ability to create, update, and delete one or more accounts associated to an organization | ||||
Ability to create, update, and delete a user | ||||
Ability to associate / disassociate a user from an account | ||||
Ability to request / remove rights for a user to publish to the UC Federated Database | ||||
Multiple user names | ||||
Make one name primary | ||||
Remove all names but one | ||||
Define aliases | ||||
remove all aliases | ||||
phone numbers | ||||
email addresses | ||||
social media addresses | ||||
street addresses | ||||
teams | ||||
roles | ||||
contributor gating / approval governance | ||||
RBAC for at least admins vs others | ||||
Open Questions
List any open questions that come to mind throughout the lifecycle of this project
...