Who can see and do what

Ganttry accounts work inside a company, and a company can be split into groups, such as regions or divisions. Every project belongs to exactly one company or one group. What you can see and change depends on your role where the project lives. Companies, groups and roles explains companies and groups in full.

The three roles#

A role belongs to one membership: you can be an Admin of one group and an Editor in another.

A project outside your companies and groups is invisible to you: Ganttry answers as if it didn't exist, rather than showing a locked button.

Moving a project to another group takes the right to delete it, plus an Admin or Editor role in the group it goes to. See Companies, groups and roles.

Field, in more detail#

The Field role is built for crews. A Field account:

• signs in to My tasks (see Work, My tasks and Calendar), its own assignments across every project it can see;
• reports progress: percent complete, work status, remaining work, checklist ticks and link attachments;
• never changes a project's structure: its tasks, their planned dates or the links between them. Its status reports do record actual dates: starting a task stamps today as its actual start, and finishing a started task stamps its actual finish;
• never sees money: task costs, contract time and the dollar totals in the schedule update narrative are left out;
• has no sidebar when Field is its only role. The top row carries My tasks, Work and Calendar, and the editor, Projects, Reports, People and Roster & equipment stay out of reach;
• never makes a crew link.

A Field account uses a full license. Report progress from a phone or tablet shows what a Field user does each day.

Master planning#

Master planning is a capability, not a role. It lets someone:

• put a project into Draft and publish it, so crews see a checked plan instead of every save (see Draft and Publish);
• open the master plan, several projects on one date axis;
• open People, who works where across every project, day by day, and manage the company's saved crews;
• restore an earlier version of a Live project from History, since crews see a restore at once. The confirm opens with Switch to Draft first picked, so crews keep today's plan until someone publishes. A project a course uses as its template or answer key can't be switched to Draft, so its confirm offers no such choice (see Saving, history and opening projects).

Who has it. Every company Admin has it because of their role. A company Admin can give it to anyone else on Company › Users & access, in the Master planning card: tick the person, and it takes effect at once. Company Admins show there as ticked and grayed out, by role; a group Admin gets an ordinary checkbox, like any other member. A Field-only account can't be given it.

Without it, you can still edit, save and restore a project that is in Draft. Your changes wait there until someone with master planning publishes them. On a Live project, Restore… shows what the restore would change and who can do it for you: they can restore it, or switch the project to Draft so that you can. It names them when there are three or fewer. In Training, a student's copy, the class board and the projects students create there need no one: anyone who can edit them restores them. You can also book people by the day on a project you can edit (but not on a student's copy or a class board in Training), one project at a time, with Book people on its Crew planning page (see Book people day by day). The same card holds Allow up to 15 projects in the master plan (the usual limit is 8).

Partner staff#

Partners are firms that resell Ganttry and run it for their client companies. Partner staff:

• see every project in every company their partner looks after, with a company Admin's full powers there;
• have their own partner dashboard for licenses and invoices;
• use no license anywhere.

Look after your clients' companies walks through their work.

The instance admin#

The instance admin runs the whole Ganttry installation, every company in it, and never uses one of your licenses.

Crews with only a link#

A crew member doesn't need an account. Anyone who can edit a project, an Editor or an Admin, can make a crew link for it, and a company Admin can make an itinerary link for one person. Whoever holds the link opens the plan on a phone with no sign-in. It shows the work, never costs or anyone's account details. A link uses no license. Send crews their links and itineraries shows how.

People you only schedule, the names on your company's roster (Roster & equipment), don't need accounts or licenses either.

Who needs a license#

• Every user with at least one membership in the company, counted once however many groups they are in. That includes Field accounts and training class accounts.
• A pending invitation holds a license until it is used or removed.
• A disabled user doesn't count, so disabling or removing someone frees their license at once.

These don't need one: partner staff, the instance admin, crews with only a link, and people on the roster who never sign in. Licenses and billing covers buying and managing licenses.

What the demo leaves out#

The demo has no company account, so it has no roles, no Home, no People, Roster & equipment or Company page, no Draft and Publish, no master plan, no Day plan, no crew or itinerary links, and no project templates, calendar standards or company columns. Its sidebar lists Projects, Calendar, Crew planning and Reports.