Staff with a verified teamplanltd.com Member account register automatically through Microsoft. External users need an administrator invitation and Microsoft verification. Your Microsoft password is never sent to this platform.

Microsoft sign-in, SSH access and your P6 account are separate. The platform manages network access; your administrator provides the P6 database connection and account details separately.

In demo mode, records and invitations are simulated, no real tunnels or emails are created, and server metrics are sample data. The Microsoft sign-in button is unavailable in demo mode.

1. In My connections, enter a computer name, acknowledge the key guidance and select Create connection.
2. Download your private key immediately. It is generated in your browser and never sent to the server. It cannot be recovered or downloaded again after you leave the page.
3. Download the launcher ZIP for the same connection. Extract it to a personal local folder and put the matching private key beside Connect-P6.cmd, using the filename in Instructions.txt.
4. Run Connect-P6.cmd on Windows and leave its window open while using P6. Configure P6 to use 127.0.0.1,11433/PMDB, then sign in with your P6 account.
5. Close P6 when finished, then press Ctrl+C in the tunnel window.

Browser-generated keys have no passphrase. Add one locally with ssh-keygen -p -f "PATH_TO_PRIVATE_KEY", or create a passphrase-protected key separately and import its public part. Follow Instructions.txt for Windows file permissions. Never share private keys or store them in a shared folder.

Launchers can be downloaded again for your own active, successfully applied connections. A launcher contains no private key or database passwords. Lost keys must be revoked and replaced. Each computer or key needs its own matching launcher package.

Only public Ed25519 keys may be imported. The active key limit includes pending connections; revoked keys do not count. The server key is pinned in known_hosts: ask your administrator about an unexpected key warning rather than disabling verification.

Sleep, a network change or an internet interruption may require restarting the tunnel and P6. Only one tunnel can use local port 11433 at a time.

Connections refresh every five seconds while that screen is open. An SSH connection does not prove that someone is working in P6, or reliably indicate whether their computer is asleep.

Disconnect closes current tunnels but permits reconnection. Revoke disables that key. Suspending a staff member ends their platform sessions and disables all their active keys; restoring the account enables previously active keys, never explicitly revoked ones.

Company staff appear after their first sign-in. Invited guests appear after their first verified sign-in. Only the owner can change roles or manage another administrator.

Individual permission overrides take priority over role defaults. A suspended account has no access. For a personal key limit, leave the field blank to inherit the role limit. The default limit is three active keys.

An agent failure means that a change has not yet been confirmed on the server. The application retries pending changes automatically. Do not treat urgent revocation as complete until it is confirmed.

An authorised administrator can invite a corporate or personal email address. Guests start with employee rights and cannot sign in before an invitation is confirmed and Microsoft verifies the matching guest identity. A matching email alone is insufficient.

Invitations require Microsoft Graph Application User.Invite.All, administrator consent, suitable company B2B policies and P6_EXTERNAL_INVITATIONS=1 on the server. Microsoft sends the invitation; personal email passcodes depend on the company's Entra configuration.

Revoking external access ends platform sessions and permanently revokes all the guest's SSH keys. It does not delete the Microsoft guest account or affect other applications. Reinviting an already suspended user does not restore their account or revoked keys automatically.

Send invitation again is available for failed or revoked invitations, or requests stuck for at least two minutes. An email may already have been sent if a later request fails; platform access stays denied until confirmed.

Host metrics refresh every five seconds while the monitoring screen is open; journal summaries refresh every minute. CPU and transfer rates need two samples after startup. The displayed interval may be longer after the screen has been closed.

CPU and RAM

CPU is a percentage of total VM capacity. Available RAM includes reclaimable memory: a low free value alone does not mean RAM is exhausted. The graph uses green for CPU and blue for RAM used excluding reclaimable memory, on a 0–100% scale. It holds the latest 60 readings collected while monitoring is open and resets on page reload.

Service resources

RAM uses service cgroup accounting or a process RSS sum where unavailable. Shared pages may be counted more than once in RSS sums. Automatic restarts are systemd's current counter, not a complete outage history.

Network and disk

Network totals exclude loopback and may include virtual interfaces. Error and drop counters are cumulative, not SQL connection failure counts. Disk I/O covers all block devices and may include layered devices.

Health indicator

Amber: CPU at least 80%, available RAM below 15%, disk usage at least 85%, recent errors, recorded automatic restarts or incomplete data. Red: CPU at least 95%, available RAM below 5%, disk usage at least 95%, or an inactive required service. Green means no configured threshold is exceeded, not a performance guarantee. A failed refresh changes the status to unknown and previous readings become stale.

Service and error history

Lifecycle history covers the available journal from the past seven days, capped at 300 lifecycle entries. Errors cover the past 24 hours, capped at 200 entries, with the latest 30 displayed. Retention and entry limits can hide older events; no records does not prove uninterrupted operation. Only error metadata is shown to protect client data. Use authorised server administration for detailed log messages.

The audit screen shows the latest 200 platform events. Private keys, Microsoft tokens and passwords are not recorded. This is platform access history, not a record of changes to P6 activities or projects.

Restart server is available only to authorised administrators and the owner. It schedules a restart of the entire Ubuntu VM after 15 seconds, including SQL Server, SSH and this platform. Notify staff and finish P6 work before confirming. There is no cancellation button in this version; do not retry an uncertain request without checking the server first. Demo mode does not perform a restart.