Workspace

Teams, Spaces, and Projects

On Start, select a Team to list its Spaces, then a Space to list its Projects. Open a Project tile to work with its data. Use an item's menu to open its details and permissions page. The header hierarchy provides navigation back to the containing workspace.

Teams are separate access boundaries. Permission inherited in one Team does not provide access in another. A Project-only or Layer-only grant may show the containing Team and Space just to let you reach that destination, without exposing sibling workspaces.

The three panes

Drag the boundaries between visible panes to resize them. Use the three centered footer buttons to show or hide Resources, View, and Details. At least one pane must remain visible. Pane widths and visibility are browser-local preferences reused across Projects, not shared project settings.

Each pane scrolls independently. In Details, General, Snapshots, and Fields can be collapsed separately. Their open state is remembered locally. Field cards have their own expand/collapse controls and an expand/collapse-all control.

Resources and View can maintain separate selections. The Details header control switches between Show View selection details and Show Resources selection details when both selection contexts are available. Check this source when Details appears to describe a different item from the selected tree row.

Resources presentation modes

Resources has three mutually exclusive modes:

• Normal: navigation, adding and deleting resources, content summaries, and property-family entries.
• Edit mode: canonical-resource checkbox selection, movement, and bulk General editing.
• Table mode: resources as rows and property families as editable columns, spanning the usual Resources and View areas.

Select a mode button again to return to Normal. Opening one special mode closes the other. Table mode keeps the selected saved View in place but hides its presentation while the grid is active. It is not a saved Table View and its local settings are not shared. See Resources.

Layers, snapshots, and Views

Use the header's Layer selector to choose All data or one accessible Layer. Only one Layer is active at a time; it affects Details and calculated Views. A user with only Layer access must remain in an accessible Layer and cannot switch to All data.

A Layer may leave the whole resource structure visible or restrict it to matching resources and their ancestor paths. A contextual edit can differ from the global default. Property labels, types, and reference configuration remain global even while a Layer is selected. See Layers.

Choose the resource snapshot in Details to inspect its Fields. New resources follow the Project timeline until switched to Local. Project timeline periods are administered centrally; local periods are editable on the resource. Changing timeline mode requires Editor or higher; managing Project periods requires Admin or Owner. See Snapshots.

Use the View selector to choose a saved View, Add view to create one, and Save view to persist its configuration. Set As of date for time-dependent calculations. Table compares data, Onepager lays out resource-list boxes, and Timeline displays periods or milestones. These are separate View types, not interchangeable modes of one saved View. See Views.

Save and connection status

Most ordinary Details inputs are drafts. Select the pane's Save after changing General fields or default/condition values. Creation dialogs and structural commands have their own save or confirmation actions. A formatted-text modal saves its value immediately; Table mode cells save through their own editor.

Changes can remain pending while the app refreshes related data and calculations. Existing completed results may remain visible during a refresh; they are not proof that a new operation has succeeded. Inspect errors as well as the footer:

The app refreshes visible data when connectivity returns. There is no documented offline editing queue. After a timeout or interrupted save, refresh and inspect the result before retrying: the operation may have completed. See Troubleshooting.

Undo

The header's Undo control represents the latest supported successful transaction for your account in the current browser tab. Hover or focus it to review the change summary; select it to undo when enabled.

Undo is not a full history and there is no Redo. Availability depends on the operation, expiry, current permissions, and whether affected items changed afterward. Conflicts disable execution instead of overwriting later edits. A successful undo, sign-out, account change, or an irreversible operation clears the available step. The step can survive a reload in the same tab when browser session storage is available; a storage warning can limit it to the current page session.

Do not assume a deletion is reversible. Resource deletion dialogs explicitly warn that the action cannot be undone, and workspace deletion permanently removes a subtree.

Favorites, recents, and navigation links

Open Favorites and recents in the header. Use Add current page to bookmark a supported page; remove a favorite with its removal control. Recents records visited supported pages and can be cleared. Each list holds up to ten entries and is stored locally for the signed-in account in that browser.

These entries return to pages, not a saved selection, Layer, scroll position, or draft. A copied Project page address does not grant access. Do not rely on it to recreate the sender's exact workspace state or unsaved work.

Roles and restrictions

Roles apply to a workspace scope and inherit into descendants. The strongest applicable assignment determines access. A lower-level assignment can elevate inherited access but cannot reduce it. Removing a direct assignment does not remove access still inherited from an ancestor.

Layer roles are scoped access, not automatic Project membership. Layer Editors can make permitted contextual value and condition edits, but cannot use that role to restructure the whole Project. File delivery and the assistant currently require Project access rather than Layer-only access.

An editable-looking control does not override your permissions. Some actions report a permission error when submitted. Linked occurrences remain read-only even for Editors until opened at their original location.

Administer a workspace

1. Open Details and permissions for the Project from the hierarchy menu, or use the Team, Space, or Project item menu on Start.
2. Review Properties, Permissions, Invitations, and, for Projects, Layers.
3. Change label, color, icon, or timezone, then save. Confirm a timezone change when prompted; existing timestamps retain their absolute instant and display in the new timezone.

Team administration requires Admin or Owner. Space and Project administration requires Manager or higher. Creating, editing, or deleting a Project Layer requires Project Manager or higher. See Layers for Layer rules and assignments.

Invite and manage members

Use Invite user, choose Single or Bulk, enter the email address or addresses, and choose a permitted initial role. Review invalid addresses before sending. The Permissions grid supports searching members, changing eligible direct roles, elevating inherited access, removing direct roles, and, for a Team Owner, transferring ownership to another member.

Inherited entries cannot be edited in place; change the original assignment or grant a higher role at this scope. You cannot edit or remove your own direct role using the grid. Managers cannot grant Manager, Admin, or Owner; Admins cannot grant Owner. Every active Team must retain an Owner. Invitations can be resent or revoked from their list. See Getting started.

Bulk invitations are processed individually, so some can succeed while others fail. Review the success and failure messages; failed addresses remain in the bulk input for correction or retry. Do not resend the whole original list merely because one invitation failed.

Delete a Team, Space, or Project

Choose Delete on its administration page and type the exact displayed label. A Team requires Owner; a Space or Project requires Manager or higher. Confirm only after reviewing the entire subtree affected.

The subtree is hidden and locked immediately, access is revoked, and permanent deletion continues in the background. Start lists Recent deletions with their status. A failed job requires administrator/support attention; it is not a restore workflow. Workspace deletion is irreversible.

Assistant availability

The header's Use AI opens an assistant when enabled for the deployment. It can inspect permitted content and execute supported requests under your access rights. Review change results and cited sources. Smaller supported write plans may execute without a separate approval step; when the app requires approval, use its Approve or Reject controls.

The assistant provides conversations, rename/delete controls, conversation search, explicitly saved memory, and result-notification settings. Private conversation text is not shared workspace documentation. Deleting conversation history does not undo data changes already made. If the assistant is unavailable, use the normal workspace controls; Layer-only access does not currently provide the Project identity needed for it.