Organizations

[opqdonut]

Check NKR's specific needs before starting implementing. Some ideas:

• add missing organization fields to db & api
  • catalogue item (add organization field to catalogue items #1916)
  • license (Add organization field to licenses #1917)
  • license attachments no need for this yet
• track organization of users (optional organization field for users #1918)
• get user organization from aai-proxy / idp – split to Support multiple organizations per user #2035 and Read groups from eDuuni #2036
• create organization-owner role that allows administration acccess only to users own organization
  • Back-end: Filter by users's organization in listing APIs
    • resource, license, form, workflow
      • remove this feature (see ADR009 POC: ADR 009 #2004) (remove filtering by organization from admin APIs #2034)
    • license attachments
    • catalogue item
  • UI: Set organization when creating object
  • Back-end: Check that user's organization matches object's organization when creating
  • Back-end: Check that user's organization matches object's organization when editing/archiving/disabling
    • catalogue item (organization-related improvements to admin api #2028)
    • workflow (allow organization owner to edit/disable/archive resources/forms/workflows #2029)
    • form (allow organization owner to edit/disable/archive resources/forms/workflows #2029)
    • resource (allow organization owner to edit/disable/archive resources/forms/workflows #2029)
    • license (feat: allow organization owner to enable/disable licenses #2031)
  • Back-end: Check that license's organization matches license attachment's organization when creating a license (not needed, see ADR009 POC: ADR 009 #2004)
  • Back-end: Check that license, form, workflow, and resource organization match catalogue item's when creating a catalogue item (feat: check that organizations match when creating catalogue item #2014)
    • remove this check (see ADR009 POC: ADR 009 #2004) (organization-related improvements to admin api #2028)
  • Back-end: Check that license organization matches resource's when creating a resource (feat: check license organizations in /api/resources/create #2022)
    • remove this check (see ADR009 POC: ADR 009 #2004) (organization-related improvements to admin api #2028)
  • UI: Only show licenses, forms, and workflows that match the catalogue item's organization when creating catalogue item
    • remove this feature (see ADR009 POC: ADR 009 #2004) (feat: allow creating items with mixed organizations in admin ui #2038)
  • UI: Only show licenses that match the resource's organization when creating resource
    • remove this feature (see ADR009 POC: ADR 009 #2004) (feat: allow creating items with mixed organizations in admin ui #2038)
  • Add RDorganizationowner1/2 users to test data
• list available organizations in config (:organizations config option #1973)
  • configure available organizations for existing installations (do any even use organizations?)
• "show only my organization" checkbox in admin listing pages (split out to "Only show my organization" checkbox for admin tables #2046)
• document organizations feature (doc: organizations #1996, doc: update docs/organizations.md #2045)
• less clear tasks / ideas:
  • possibility to limit api key to organization?

[opqdonut]

ADR009 (#2004) causes changes to organizations. Edited task description accordingly.