Companies, groups and roles

Ganttry organizes people and projects by company, and a company can be split into groups — regions or divisions. Every project lives in exactly one company or group, and a person's role in each one decides what they see, what they can change and what they can delete. Ganttry enforces it for every request: a project outside your companies and groups isn't hidden behind a grayed-out button, it simply isn't there for you.

Where to find it#

A company admin manages all of this on the Company page: Company in the sidebar, then the Users & access section for people and roles and the Organization section for groups. Everyone else sees the result — the projects they can open on Projects, and the company and group headings on Home.

Companies and groups#

A company is the top level: its people, its projects, its licenses and its settings. Groups are optional divisions inside it — use them to keep projects apart by region or division.

• Organization › Groups lists each group with how many projects it holds, and Rename… and Delete beside it. + Add group… asks for a name (for example a region).
• A group that still holds projects can't be deleted — move or delete its projects first. Deleting an empty group asks first, and its members lose that membership.
• With no groups yet, the card reads "No groups yet. Use groups to keep projects separate for regions or divisions."

When you belong to more than one company or group, the New project dialog shows a Company or group row so you pick where the new project lives; importing a file asks the same question its own way. Both start on the company the scope control at the top shows, never on one where your role is Field, and Make a copy… starts on the company or group of the project it copies when that one is in its list. Home groups its rows under company and group headings, and a project's ⋯ menu on Home has Move to group… where you may move it (see Moving a project to another group).

Moving a project to another group#

File ▾ → Project settings… has a Group row. Pick another group of the same company, or No group for the company level. Ganttry asks first — "Move this project to North? Who can open it changes with its group." — and moves it at once; it isn't part of the dialog's Save. The line under the row then reads Moved to North., or says why the move was refused. With the keyboard, the arrow keys move through the groups without asking; the question comes when you leave the list or press Enter. After a move the row is read again: where you can no longer move the project, it shows the new group as text. Move to group… in a project's ⋯ menu on Home opens the same row in a small dialog; it's offered only on projects you have the right to delete.

• You need the right to delete the project (a company admin, or an admin of its group) and an Admin or Editor role in the group it goes to. The list only offers groups you may move it to.
• Where you can't move it, the row shows the group's name as plain text, and the Home dialog reads "This project can't be moved to another group."
• Training course projects never move, and nothing moves into a course group.
• People in the group it left and in the group it joined both see the move in their activity feed.

Roles#

Each membership carries one of three roles: Admin, Editor or Field. Roles are per membership — the same person can be an Admin of one group and an Editor in another. What each combination opens:

Any Editor or Admin can create, edit and archive projects where they have that role. Delete only shows where you have the right to use it. Company access does not include the company's groups: a group's projects are opened by that group's members and by company admins. Publishing the plan crews see, restoring an earlier version of a Live project and opening the Master plan need the Master planning capability, which company admins hold by role and others are granted — Who can see and do what has the full picture, and the partner program covers partner staff.

Setting roles#

On Users & access, the Memberships matrix lists each person down the side and the company and its groups across the top. Each cell is a menu: No membership, Editor, Admin or Field. A change saves as soon as you pick it.

• A new person gets their first memberships when you add them (the Member of boxes on the Users card — see Invitations and password resets).
• Removing all of a person's company and group access deletes their account. Their projects stay with the company or group; their sessions, saved views, PDF presets, preferences and any unused invite or reset links go with the account. Partner staff keep their accounts.
• Every person with at least one membership, unless disabled, uses one license — see Licenses and billing.

Profile pictures#

Everyone gets a profile picture: a colored circle with their initials, with nothing to set up, or a photo they upload from Profile… in the avatar menu (see Your account). Pictures show at the right end of the top row and in the Company page's Users table. A picture is only ever shown to people who share a company with its owner, and to the instance admin.

Presence#

Open projects show who else is there right now.

• An avatar stack in the top row shows who else is viewing the same project (a count on phones), and the status line announces people joining and leaving.
• Each viewer's selection shows live in the grid, in their own color: an outline on their active cell with a brief name flag, and tinted row numbers on the rows they have selected.
• A pencil dot on someone's avatar means they have unsaved edits in flight.
• When a teammate saves, everyone without unsaved work of their own picks up the new plan at once — the changed cells flash in that person's color, and the status line says "Updated by" and their name. Anyone with unsaved work keeps it and is warned that a review is coming; the usual conflict review follows (see Saving and history).
• While History, Save a version…, or anything opened from History (Look, Compare with now or a restore) is open, a teammate's save waits and lands when you close the last of them.
• The Projects page shows a live "N viewing" badge on any project someone has open; hover it for the names.

Presence follows the same rules as the project itself — you only ever see the people who can open it. For training sessions and meetings, Present to everyone viewing… lets one person lead everyone's screen; see Getting around.

Who can use it#

Everyone signed in to a company sees the projects their memberships allow. Groups, users and memberships are managed by a company Admin (and by partner staff for the companies their partner looks after). A group's own Admin can delete that group's projects but does not manage people. See Who can see and do what.

Good to know#

• Your own name and email are yours to change in Profile… — see Your account.
• For someone who also has access outside your company, the Company page hides the actions that reach beyond it (editing their name or email, their password, disabling, re-inviting). Remove still works: it only takes away their access to your company.
• Names on past records — who saved a version, a roster entry, the activity feed — keep the name they had at the time.
• A browser-only session of Ganttry (the demo, or local projects) has no companies, groups or presence.