Import action should not ignore Selective Access for a Workspace Administrator

Import action should not ignore Selective Access for a Workspace Administrator

Description of the enhancement required:

Workspace admin with applied selective access to only one region had affected data in other regions because selective access does not work on Workspace admins.

 

An example of the enhancement:
As a workspace admin if I change my profile to only have access to a specific region, and then run an import, it clears the data for all regions but imports the data for only the region I have access to. It would be better if it either
1) (ideally) both cleared the data for the region I have selected and imported the data for the region I have selected
2) or both cleared the data for all regions (overriding the security settings) and imported the data for all regions (for the region I have selected)

 

How would it help your business process:
We may have people working in the model that are workspace admins alongside non-workspace admins. Other people working on their list would be confused to why their data was being modified.

8 Comments
Community Manager
 
Status changed to: Considered for Future Roadmap
Master Anaplanner/Community Boss

As a "workspace admin" flagged user, I would like to have the behavior consistent with the security and roles set up to the user when it is launched an import action. 

 

Currently, when a user is flagged as "workspace admin" if launches an import action can update data cells that the user does not have access (through "security selective access" or DCA flags). 

 

 I do not find any advantage that a user has the ability to update read-only data cells (or cells that the user does not have access) only because he/she is flagged "workspace admin". This is happening even the role associated with the user is other than "Full access". 

 Maybe this was implemented to have a high-level user to bypass the front-end restrictions, but, in my opinion, it is more important to have the user consistent with their role and security when using the front-end. 

 

The "workspace admins" are consistent with their security and roles when they are using the front-end, except when they launch import actions. Why have this exception? 🙂

 

I hope it will be solved. 

 

Thanks

Alex

Community Manager
 
Status changed to: Your support is needed
Master Anaplanner/Community Boss

Especially when you want to do testing of DCA, have to turn off the WA and then have it turned back on again. Very frustrating.

Master Anaplanner/Community Boss
Community Manager

Hi @andrewtye, are you looking to merge the two ideas? Thanks. 

Master Anaplanner/Community Boss

Hi @Miran - yes because they read very similarly albeit this one is slightly more wide ranging than the other ie takes into account user role/.

Community Manager

Hi @andrewtye, I've gone ahead and merged the ideas and kudos. 

Users Online
Currently online: 63 members 444 guests
Please welcome our newest community members: