GoProject

Administration

First login and the administrator account

Securing the initial account, the first settings and the first space and project.

Sign in

A new system has one account, and it belongs to a system administrator: sign in with it. If the first screen is Set your own password, the password you signed in with opens only that screen; choose your own to go on. A system without a licence shows the licence screen and nothing else until a licence key is added there.

Immediately

  • Administration, General settings: the Site address people open GoProject at, and the system name
  • Administration, Emails and notifications, Outgoing mail: your SMTP server, then Send test email
  • Administration, Security, Sign-in: decide whether two-factor authentication is required of everybody. Nobody can set it up for themselves before that; once Require it of everybody is switched on, everybody it covers, you included, sets up an authenticator app

Creating the first space

As a system administrator, open Spaces and choose New space. Give it a name, a key such as PAY and a description. The work item types are not the space's own: they are kept in the system's catalogue under Administration, Work item configuration, and each project chooses which of them it uses.

Creating the first project

Open the space, go to Projects and choose New project. Start from a template that sets the project up, or from a blank project, for which you pick a name, a key and a type: Scrum, Kanban, Help Desk or Internal. Then open the project's settings to switch modules on (see Module switches). Who sees the project is decided in the space tab Access and people; under Users and Roles in the project's settings people are given their roles.

Adding users

Local accounts are created under Administration, Users and groups, Users, New user. Choose whether the person is internal or external (a client or partner), and what the account opens. A directory or single sign-on can be connected instead. People are never deleted, only deactivated, which also ends their sessions.

Audit

Sign-ins, user changes and administrative actions are written to the append-only audit log; a sign-in is recorded with the address it came from. The log is read under Administration, Audit trail, and through the audit export described under REST API, tokens and audit export.