Using Siebel Tools > Using Siebel Tools > Workspaces Administration >

Controlling Access on Non-Workspace Objects

Currently, the following object types and their child objects remain as non-workspace objects:

• Repository
• Project
• Table
• Task
• Workflow
• Type
• EIM table
• Dock objects
• Schema maintenance
• Server components

Only one single public version of the object is available for all users. Hence, configuration on instances of this object is centrally controlled by the workspace administrator, who can lock all relevant projects and objects. Developers are able to configure the respective objects or projects after their requests to release the locks on these objects or projects are granted by the workspace administrator.

For changing the existing database schema or adding new tables to the database schema, all users must follow the same process that is currently followed by all development teams; that means, respective teams need to cooperate with the workspace administrators for any change that is required in the database schema of their applications.

For Workflow and Task configurations, developers must ensure that only the 0th version on the master database exists.