Consortia (Cross Tenant) (UXPROD-794)

[UXPROD-1762] Staff with appropriate privileges can edit and/or view financial data belonging to other consortium members. Created: 05/Jun/19  Updated: 04/Nov/22

Status: Open
Project: UX Product
Components: None
Affects versions: None
Fix versions: None
Parent: Consortia (Cross Tenant)

Type: New Feature Priority: P4
Reporter: Hkaplanian Assignee: Unassigned
Resolution: Unresolved Votes: 0
Labels: consortia, suppress-from-capplan
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Issue links:
Cloners
clones UXPROD-802 Staff without appropriate privileges ... Closed
Epic Link: Consortia (Cross Tenant)
Report Functional Area(s):
Consortia
Kiwi Planning Points (DO NOT CHANGE): 1
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R5
Rank: Cornell (Full Sum 2021): R5
Rank: Duke (Full Sum 2021): R4
Rank: 5Colleges (Full Jul 2021): R5
Rank: FLO (MVP Sum 2020): R4
Rank: GBV (MVP Sum 2020): R4
Rank: hbz (TBD): R1
Rank: Lehigh (MVP Summer 2020): R4
Rank: MO State (MVP June 2020): R4
Rank: TAMU (MVP Jan 2021): R5
Rank: U of AL (MVP Oct 2020): R5

 Description   

Description:
Staff with appropriate privileges can edit and/or view financial data belonging to other consortium members.

Notes:
FOLIO can do this today. However, the ultimate wish is for a person to have this ability without adding a user record to each tenant.



 Comments   
Comment by Lloyd Chittenden [ 03/Jun/20 ]

We would not want consortium members to be able to view or edit financial data from other accounting units, but we would like to be able to create a super user (probably consortium staff) who can view everyone's financial records simultaneously.

Comment by Cate Boerema (Inactive) [ 14/Jul/20 ]

Kelly Drake, this feature is assigned to Q2 2020 but it's open and has no dev team. Can we remove the fix version?

Comment by Kelly Drake [ 20/Jul/20 ]

Cate Boerema - yes I have removed the fix version. Not sure how it got there in the first place.

Generated at Fri Feb 09 00:18:19 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.