Unable to make changes to sandbox, unless given admin access

[sreesuku]

Hi Team,

I want to enable Sandboxes for a specific blue group for TM1 Web.

I have given 'Grant' option in capability assignment for 'Personal Workspace write back mode' and 'Sandboxes', but users are not able to make changes to the sandboxes. They can delete and create their own sandboxes, but not able edit. My cube is also assigned to the blue group

But, when I give them the 'Admin' access, they can edit and commit the sandboxes.
Is there any other way I can give them the desired sandbox access ? Or Am I missing something here ?

Note : My primary requirement was to give users access only to play around with sand boxes, and not to allow them to 'Commit'. But I have read in some of the posts in this forum that its not possible. Some work around that also will be helpful. But my priority is the issue mentioned above.

Regards
Sree

[sreesuku]

Gurus,

Help me pls ....

[sreesuku]

I have got this issue resolved.. It was my mistake. I gave only 'Read' permission for the Group against the cube. It should have been 'Write' . I corrected it.

Now I have another issue. Users are able to write back from 'Base' version and their own Sandbox.
(Base version by directly changing the values and recalculating, Sandboxes by changing the values and committing) . Is there anyway I can disable the write back mode for the 'Base' version. So that users can write back only from their version of Sandbox ?

[lotsaram]

Now I have another issue. Users are able to write back from 'Base' version and their own Sandbox.
(Base version by directly changing the values and recalculating, Sandboxes by changing the values and committing) . Is there anyway I can disable the write back mode for the 'Base' version. So that users can write back only from their version of Sandbox ?

If a user has write access then they have write access! The sandbox is an intermediate "holding area" where users can write and model data they have access to before committing the sandbox changes back to the base model. Without having write access to the relevant section of the base model there would be no way for users to save the sandbox to the base model. But you can't stop a user writing to base if they have access, if you take away that access then changing the sandbox won't work either.

If you want to allow users some ability to model without being able to write back to the "real" data then you would need to incorporate such a version/scenario into the real dimensionality of the cube.