The Workspace

   Composer This topic is related to Transact Composer.  |   Form Builder |  v4.3 & Higher   This feature is related to v4.3 and higher.

Workspace Hierarchy

The Root level is the top of the Composer environment; this is at the server level. You access Composer through a recommended browser and assigned URL If you have opted to host Composer yourself and not in the community cloud some of the issues of hosting your own environment may not be covered in this document.

The Composer workspace is organized into a number of Accounts. Above these lies the Avoka-administred Root level. You will have been assigned to one or more of these Accounts, which will be the areas you will be administering. The Account level usually corresponds to the Enterprise level in the real world. An Account can have many Organizations, usually corresponding to the department level in the enterprise.

Floating above the Root are the Global Libraries and Access Control. Global Libraries are, as it were, dynamic super libraries, in the sense that changes to these will ripple through the entire system of account-level libraries. More on libraries will follow.
We have placed, somewhat arbitrarily, Access Control outside of the Workspace, mainly because it lies outside of the Workspace structure (though not entirely, as we will see). Also, although you can create roles and assign users, all your access control settings are not held under the account level like, say, libraries.

In most usual account configurations, the end users are normally granted rights to set up Projects and create forms under them. The Project level is often used by designers as their personal space. However, you decide whether you will adhere to this scheme.