Anaplan users and inherited user rights for models in the same workspace (workspace admin)

ravinderQuilter · 2024-07-22T11:34:41+00:00

There was an error rendering this rich post.

I think Anaplan should change the inherited access rights to models in workspaces.

When creating users, it is easy to give a user access level when creating a user BUT the problem is this becomes inherited in other models in the same workspace. There is a workaround - give no access when setting up the user then specify access rights later, per model in the workspace.

But this can be often overlooked.

I would recommend a better user access setup for workspace admins at model level. There was talk about this few years ago but nothing has materialised I believe.

Thank you.

Accepted answers

ravinderQuilter

The issue was the workspace admin checkbox; if one deselects it; it applies this setting to all other models in the same workspace; I have just tested this. But if I want only selective workspace admin access to certain models in the same workspace; this becomes more challenging.

rob_marshall

@ravinderQuilter

You never mentioned the WSA piece, just the user piece. And since the WSA setting is a workspace setting, it makes since that when this is changed, it applies to all models within the workspace. With that said, I will grant you another column would be nice for a "model admin" that ‌applies to that model and that has been requested before in Idea Exchange.

All comments

rob_marshall

@ravinderQuilter

I believe the default is No Access to other models within the workspace when ‌adding a new person to a certain model.

ravinderQuilter

That is correct @rob_marshall

The only issue is if one changes the default access to something else. When this happens, the system assumes the same rights to other models in the workspace; which should not be the case. In effect, specific model access in the same workspace becomes more tricky.

I recommend an easier model user access system to prevent the above.

rob_marshall

@ravinderQuilter

I don't believe you are correct as the model access is based on Roles which are model specific. If I have the same role name in multiple models within a workspace and I change the role of a user in one model, it will not update or change the role in the other model.

thank you #rob_marshall

I have started an idea on this topic:

Workspace Admin at model level — Anaplan Community

https://community.anaplan.com/discussion/158716/workspace-admin-at-model-level/p1?new=1

Quick Links

Can you help?

Unanswered questions

Request for Workflow Design: End-User Report Finalization & Stakeholder Notification with Version Co
Hi everyone, I'm looking to design a workflow and would appreciate your input or guidance on how to set this up effectively in Anaplan. So, the goal is: Once end users complete their data input, they should be able to trigger a process that: Notifies stakeholders via email with a link to a report. The report includes: A…
OAUTH 2.0 vs Google Sheets Extension
Hi, My org is looking to explore leveraging Google Apps script to extract data out of Anaplan and update already built templates in Google Sheets. We use the Anaplan Extension currently but find it crashes often with the amount of tabs, data, etc. Has anyone used both Anaplan OAUTH 2.0 API and Goolge Apps Script to write…
Exports with anaplan using informatica connector
I'm trying to execute an Action to export data with the use of a Mapping in Informatica. But it gives us null rows .If we export directly from Anaplan , the export file has all the rows filled. Both exports have same number of rows but in the informatica export the values appear as blank. This issue is with only some…