Company Administrator Guide

Document ID: M17-CERT-001-D2

Audience: Customer company administrators

Last updated: 2026-08-12

Applies to: Jakten Platform 2.0

1. Administrator responsibilities

Company administrators manage the local deployment and decide who can use each licensed product and project.

Your subscription is managed through Jakten commercial services. Project, Estimate, and Risk data remain on your own Platform deployment.

2. Administration map

Open Administration from the Platform left navigation. The administration subnavigation contains:

If a destination is unavailable, your current role lacks its required permission.

3. Activate and validate licensing

After purchase, securely retrieve the activation key from the checkout result or onboarding email.

1. Sign in as an administrator.
2. Open Administration → Licensing.
3. Enter the activation key under Activate subscription.
4. Select Activate with key.
5. Complete legal acceptance if prompted.

Activation is performed once per company deployment: on the single-user PC or the office server, not on every workstation.

After activation, confirm:

• Status is Active and operational mode is Normal.
• Risk and/or Estimate entitlements match the subscription.
• Purchased, assigned, and available seat counts are plausible.
• Required legal acceptance is current.

Use Validate after extended offline use, a billing correction, a renewal, or a licensing warning. Validation contacts the licensing service; routine project work stays on your deployment.

4. Create users and assign roles

1. Open Administration → Users.
2. Under Create user, enter the display name, email, initial password, and initial role.
3. Select Create user.
4. Select the new user to review details, roles, and effective permissions.
5. Provide credentials securely. Platform does not email invitations automatically.

Use the user detail panel to add or remove roles. Assign only the permissions needed for the person's work. Keep at least two trusted administrator accounts when possible.

To reset a password, select the user and Reset password. Deactivate accounts that no longer require access; do not reuse one person's account for another person.

5. Manage project access

Product seats and project access are separate. A user needs both before opening project work.

1. Open Administration → Project Access.
2. Select the project.
3. Add the user and choose the appropriate project membership role.
4. Save and confirm the member appears in the project.

Project managers may also manage members from the project workspace when their permissions allow it.

6. Enable products and assign them to projects

Enable licensed products under Administration → Products. Current routable products are Jakten Risk and Jakten Assurance.

Enablement makes a product available to the company; it does not by itself grant a seat or assign the product to every project.

For each project:

1. Open the project Overview.
2. Assign and activate the required product workspace.
3. Create or select a working Estimate Version.
4. Confirm the product card becomes available.

Risk and Estimate both use the selected Estimate Version as launch context.

7. Assign seats

Open Administration → Licensing → Seats.

1. Select the user.
2. Assign the paid product seats they require, such as Risk or Estimate.
3. Save and verify utilization.

Rules:

• Seats are named-user assignments, not concurrent-use tokens.
• A user cannot receive a paid product seat beyond the purchased limit.
• Platform access is derived from active paid product entitlements and is not sold or managed as a separate paid module.
• Revoking a user's final paid product seat removes their derived Platform entitlement.
• An administrator needs a seat for any product they personally open; administrator role alone is not a product seat.

Revoke unused seats before reducing subscription quantity. After a seat or billing change, validate licensing if the local view does not refresh.

8. Manage company standards

Open Administration → Standards before creating production projects or importing estimates.

Publishing a company metric makes it a governed standard. Current Estimate Versions apply published standard metrics through the estimate-state workflow; users do not manually activate metrics per project.

Publish standards deliberately. Existing projects and frozen product evidence preserve their recorded identity rather than silently changing to match a later standard revision.

9. Billing and access restrictions

Platform shows the subscription term, entitlements, seat utilization, and enforcement state. Invoices, payment methods, quantity changes, and cancellation are handled through the Stripe Customer Portal or Jakten support.

After resolving payment, select Validate. Contact [email protected] if normal mode does not return.

10. Administrator recovery

If another administrator can sign in, they should reset the locked user's password under Administration → Users.

If the sole administrator cannot sign in:

1. On the sign-in page, select Administrator recovery.
2. Generate and copy or download the Recovery Request.
3. Email it to [email protected] from the billing contact address with the company legal name and callback number.
4. After identity verification, apply the signed Recovery Response in Platform and set a new password.

Do not send a password or full activation key by email.

11. Deployment care

• Review About & Deployment regularly for version, update stage, migrations, compatibility, and Deployment Health.
• Back up the Platform database and the host-local estimate.db and epc-risk.db product stores as one coordinated deployment set.
• Test recovery before relying on a backup policy.
• For office deployments, keep the Platform Server running and restrict its port to the office LAN or approved VPN.
• Apply suite updates in the order and maintenance window described in the Suite Updates Guide.

12. Support requests

Include the company name, administrator email, Platform version, Deployment Health summary, exact error, and actions already tried. Share only the activation-key prefix, never the full key.

Related documentation