Workarea Administration

The Settings page lets workarea administrators configure how items, documents, workflows, and traceability work within a workarea. Only users with the Admin role can access settings.

Settings Sidebar

The Settings page opens in the Workarea scope of the administration rail — a scope switcher, a quick filter (⌘K), and collapsible groups that open one at a time. Navigating Administration covers the rail, the scope switcher, the workarea switcher, and the filter in full; this article focuses on the settings themselves.

The Workarea scope organizes settings into five groups:

GroupTabs
GeneralProject, Members, Explorer Sidebar
Data ModelWork Item Types, Document Types, Link Types, Enumerations, Icon Library
Workflow & VerificationWorkflow Definitions, Workflow Assignments, Iteration Types, Verification Configuration
Quality & VariantsSuspect Links, Integrity, Variant designations
Extensions & LogsPlugins, Logs

Installation-wide settings — users, workareas, groups, and global configuration — live in the Site scope; see Site Administration.

Project Settings

The Project tab shows basic workarea information:

  • Workarea ID — Read-only identifier set at creation
  • Workarea Name — Editable display name
  • Group — The group this workarea belongs to (read-only)
  • Description — Optional description of the workarea

Explorer Sidebar

The Explorer Sidebar tab controls the left sidebar’s layout. The sidebar is a list of root folders: the default roots (Workspace, Items, Manage, Variants, Reviews) are built into ROPARC, and you can add custom roots of your own — a Favorites area, for instance.

  • Reorder roots — Move any root, default or custom, up and down the sidebar.
  • Add a custom root — Give it a name and an icon; it renders as its own collapsible section.
  • Add folders — Nest folders inside a custom root, and folders inside those.
  • Add shortcuts — Point at anything that already lives in a default root: a document, a dashboard, a saved view, a work item type, an Explorer folder, or a page such as Change Requests. A shortcut to an Explorer folder expands in place to show that folder’s contents.
  • Move entries between roots — The Entries list shows which root each built-in page sits in. Put Checklists under Manage instead of Reviews, or pull Change Requests out of Manage into a custom root. A moved page leaves its original root rather than appearing twice — that is the difference between moving an entry and adding a shortcut to it. A root whose entries have all moved away disappears from the sidebar. Entries generated from live configuration — the Explorer tree and the per-type Items rows — always stay where they are.
  • Hide entries — Set an entry to Hidden for pages the workarea doesn’t use; an organisation that doesn’t work with verification can take Verification out of the sidebar. Hiding is navigation only: the page’s URL still works for anyone who has the link and no data is touched, so this tidies the sidebar rather than switching a feature off. A hidden page also disappears from any custom root that shortcut to it, and un-hiding restores it to wherever it was placed.

Shortcut names follow their target, so renaming a document renames its shortcut. If the target is deleted, the shortcut stays visible but greys out, so you can find and remove it.

Changes apply when you press Save, and the layout is shared by everyone in the workarea.

Configuration Inheritance

ROPARC uses a three-level configuration hierarchy:

  1. Global configuration — System-wide defaults (managed by site admins)
  2. Group configuration — Defaults for all workareas in a group
  3. Workarea configuration — Specific settings that can inherit or override parent levels

This means your workarea may have item types, link types, and enumerations inherited from its group or global configuration — they appear with an Inherited badge in the settings tabs. See Configuration Inheritance for the full model with examples, and the individual topics below for each configuration area.