This content has been marked as final. Show 1 reply
Along with granting privileges on the specific tables, you would need to grant ACCESS_WORKSPACE using dbms_wm.grantWorkspacePriv on the specified workspace. Without granting any other privileges, the user would not be able to create additional child workspaces, or merge/rollback the workspace. Then, you would need to create a logon database trigger that places the user in the appropriate default workspace.
However, a user is always able to access the LIVE workspace. There currently isn't any way to prevent that.