Company Administrator Guide

Document ID: M17-CERT-001-D2

Audience: Customer company administrators

Last updated: 2026-10-04

Applies to: Jakten Platform 2.0

1. Administrator responsibilities

Company administrators manage the local deployment and decide who can use each licensed module and project. Much of the day-to-day project work no longer needs an administrator: Editors create and set up projects, and project managers staff and archive their own projects.

Administrators buy and change the subscription in Platform, under Administration → Licensing → Subscription and billing (section 10). Payment and card details are handled by Stripe, never by Jakten. Project, Assurance, and Risk data remain on your own Platform deployment.

2. Administration map

Open Administration from the Platform left navigation. It has three groups:

Estimate Statuses and Company Metrics appear only when the company is licensed for Jakten Assurance. If another destination is unavailable, your current role lacks its required permission.

Activity lists changes newest first. Filter by kind, dates, person, or project, and select Load more for older activity. Administrators can select Export CSV to download everything the filters match; the export is itself recorded. Each project also shows its own Activity card on its Overview: who created, closed, or reopened Estimate Versions, and who changed its members and modules.

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 Full access.
• Risk and/or Assurance 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, and initial password, and choose a company role. No role is preselected.
3. Under Module seats (optional), choose the module seats the person needs. Each shows how many are available. A user without a seat cannot sign in while seat enforcement is on.
4. Select Create user.
5. Select the new user to review details, roles, and effective permissions.
6. Provide credentials securely. Platform does not email invitations automatically.

The Users table shows each person's company role, module roles, and seats, and marks an active user who cannot sign in because they hold no seat (Can't sign in: no seat).

Company roles

Every user holds exactly one company role. Choosing a different role on the user detail panel replaces the old one; before you select Save, the panel shows what the change adds and removes.

Reviewer and Executive are read-only: no project membership or module role gives them a change, including managing a project's team. Keep at least two trusted Administrator accounts when possible; the last active Administrator cannot be demoted or disabled.

Standard User is retired. It can no longer be assigned. If anyone still holds it, the Users page lists them under Standard User is retired with a proposal for each — Move to Reviewer, or Remove Standard User when their other role already covers everything it gave. Confirm each proposal after reading what the person gains and loses. Several people can be confirmed together only when none of them loses anything. Every confirmation is recorded in Activity.

Module roles

Within each module the company has turned on, a user also has a module role:

You do not have to set module roles. Each user gets a default that follows their company role, marked (default) on the user detail panel. Set one only to narrow what someone can do in a module — for example, an Editor who should only read estimates. A module role can never give more than the company role allows; roles it would widen are shown as unavailable. A module role is company-wide; what a person can do on a particular project still depends on their project membership.

Standards manager

To let an Editor maintain company standards (Version types, dropdown lists, profile field rules, and the Attach to new projects switch on classification libraries) without making them an Administrator, turn on Standards manager on their user detail panel. Administrators already have it; Reviewers and Executives cannot hold it.

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.

Disabling a user releases every seat they hold, so the seats are free for someone else straight away. The confirmation lists the seats that will be released. Enabling the user again does not restore them; assign seats again under Administration → Licensing → Seats.

5. Manage project access

Module seats and project access are separate. A user needs both before opening project work. Administrators are the exception to membership: they work on every project without being a member, but still need a seat for any module they open.

Each project member has one project role:

A project role never gives more than the person's company role: a Reviewer or Executive who is a Manager still changes nothing.

Project managers staff their own projects. An Editor who is a Manager of a project adds and removes its members from the project's Members page, without an administrator. Administrators can do the same for any project from Administration → Project Access or the project's Members page:

1. Open the project's Members page (or Administration → Project Access and select the project).
2. Under Add member, choose the Company user and a Project role, then select Add member.
3. Confirm the member appears in the list.

• Adding a member never assigns a seat. The Members page shows which module seats each member holds (while seat enforcement is on). A member only needs seats for the modules they will use; an administrator assigns seats under Administration → Licensing → Seats.
• A project always keeps at least one manager. Removing or demoting the last manager is refused: make another member a manager first.
• Archiving. A Manager who is an Editor, or an Administrator, archives a project from its Settings → Lifecycle (Archive project) and brings it back with Return to active. Restoring a deleted project from the recycle bin stays with Administrators.

Every membership, archive, and module change is recorded in Administration → Activity and on the project's own Activity card.

6. Set up projects and choose their modules

Turn modules on for the company

Turn modules on under Administration → Modules. The page lists every module the Platform registry

carries, with its status (On, Off, or Coming soon), its license state, and a Turn on / Turn off action

where you have permission. The modules available to turn on today are Jakten Risk,

Jakten Assurance and Jakten Quote; the rest show as Coming soon. When license enforcement is on, a module can be

turned on only while the company license covers it — otherwise the page shows the license reason (not

activated, expired, or not licensed) instead of the button. Turning a module off is always allowed;

turning it off does not delete anything, but people can no longer open the module on the projects that

use it until you turn it back on. Turning a module on or off is administrator-only.

Turning a module on makes it available to the company; it does not by itself grant a seat or add the module to any project. Opening a project never adds modules to it either: each project uses only the modules chosen for it.

Set up a project

Administrators and Editors create projects. Select Projects, then Create project. Set up a project walks through these steps, and nothing is saved until Create project on the last step, so a half-created project is never left behind:

If the server refuses something, the wizard returns to the step that needs fixing. Steps you skip do not block anything: until they are done, the project Overview shows Finish setting up this project with a link for each (enter driver values, create the first Estimate Version, add team members, retry a module activation).

Modules are switched on straight after the project is created. The result screen shows each module as Active or Not activated; Retry activation tries again without creating anything twice.

Change a project's modules later

Open the project, then Settings → Modules. Each company module shows its state on that project:

Adding a module and retrying need a Manager who is an Editor, or an Administrator. Turning a module on for the company stays administrator-only.

Risk and Assurance both open on the project's working Estimate Version. A project with Assurance but no Version yet shows Create the first Estimate Version when someone opens Assurance.

7. Assign seats

Open Administration → Licensing → Seats.

1. Select the user.
2. Assign the paid product seats they require, such as Risk or Assurance.
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.
• If the purchased count drops below the seats assigned, the most recently assigned people beyond the paid count lose access to that product until seats are revoked or bought (see section 10).
• 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.
• Disabled users hold no seats and are not offered in the seat list.

To buy more seats, or to reduce the count at your next renewal, open Administration → Licensing → Subscription and billing. A reduction cannot go below the seats assigned, so revoke unused seats first. New seats appear once Stripe confirms payment; the page refreshes when you come back to the app, and Refresh checks again.

8. Company settings

Open Administration → Company → Settings. Viewing is open to every company role. Changing the profile, regional defaults, branding, and governance requires the Administrator role; Version types, dropdown lists, and profile field rules can also be changed by a Standards manager.

The page has two halves, and they behave differently on purpose.

Profile — display name, legal name, and postal address. Select Save profile and the change takes effect for everyone immediately. Reports use the branding profile's own display name, which is separate.

Regional defaults — currency, measurement system, language and region, time zone, and the month your fiscal year starts. These are a published standard, so you edit a draft and then publish it:

1. Change the settings you want.
2. Select Save draft. Nothing outside this page has changed yet.
3. Select Publish, read the confirmation, and confirm.

The confirmation names every setting that differs from what is live, and says how many of your projects keep the defaults they already captured. Publishing does not reach a running project. Each project captured the published defaults when it was created and keeps them; only projects created from now on use the new ones.

Language and region, and time zone, control how dates and numbers are written across the suite. Leave either unset and each workstation uses its own — which is what happens today if you have never opened this page.

Currency here describes your company. It is not the currency an Assurance estimate reports in: an Assurance estimate's currency is the one confirmed when its workbook is imported. Assurance import accepts USD only today, and Settings warns you when you choose anything else.

Branding

Branding — the logo and the wording printed on reports: display name, report footer, cover subtitle, and an optional contact block and disclaimer. Changing branding needs its own permission, held by the Administrator role.

Branding is published the same way as the regional defaults: edit, Save draft, then Publish and confirm. Projects already running keep the branding they captured when they were created.

To add or change the logo:

1. Under Logo, choose a file. It must be a PNG or JPEG, at most 2 MB and 4000 pixels on a side. The platform checks the file itself, not its name.
2. The preview appears once the image is read. Choosing a logo changes nothing on its own.
3. Save draft, then Publish.

A company with no logo is fine: reports print the display name instead. Select Remove logo to go back to that.

Every logo you upload is kept, even after you replace it, because a report issued with the old logo must still be able to show it.

Estimate Version types

Version types are the names your estimators choose from when they create an Estimate Version: 30%, 60%, IFC, Forecast update and so on. Every company starts with the Jakten set, and you can rename, reorder, describe, add and retire types to match how your company works.

Each type maps to a stage — Conceptual, Preliminary, Budget, Control, Definitive, Baseline, Forecast or Change — and may name an AACE class. The stage list is Jakten's, and it is what comparisons across projects use, so two companies that call the same milestone different things still compare.

Version types are published the same way as branding: edit, Save draft, then Publish and confirm. Editing them needs the Standards manager permission (Administrators hold it; see section 4).

• A change reaches new Versions only. A Version keeps the name, stage and number it was created with. Rename "60%" to "60% design" and the existing 60% Versions still read "60%".
• A project can hold several Versions of one type. The second is labeled "60% Rev 2", the third "60% Rev 3". A revision is for a re-issue that must stay on record, not for every re-price.
• Retire, don't delete. A retired type leaves the list estimators choose from, and every Version that already has it keeps it. You can reactivate it later.
• Names are never reused. A name cannot end in "Rev" and a number, and it cannot be one another type has ever held, in any capitalization — otherwise two different Versions could end up with the same label.

A Version created by mistake is voided from the project's Versions list, not renamed. Only a Version with no work in it can be voided, and voiding is permanent: it stays listed as Voided, with who voided it and why, and its revision number is not reused.

Dropdown lists

Dropdown lists are the controlled vocabularies your projects choose from: Market sector, Project type, Delivery method, Business status, Country, State or province, and Currency. Every company starts with the Jakten set — the full country and currency lists, US and Canadian states and provinces, and a starting set of sectors, project types and delivery methods — and you can add, rename, reorder and retire entries to match how your company works. Projects will use these lists for their profile fields.

Pick a list from the row of tabs (each shows how many entries are active), then edit it in place. Editing needs the Standards manager permission; without it you see the lists but cannot change them.

• Edits are live. There is no draft or publish. Adding, renaming, reordering, retiring and reactivating take effect as soon as you save.
• Renaming changes the name everywhere. The code behind an entry never changes, so a project that already uses it keeps working; only the name people see changes.
• Retire, don't delete. A retired entry leaves the choices on new projects but stays on the projects that already use it, and you can reactivate it later. An entry is never deleted.
• Codes are fixed. A snake-case list (like Market sector) makes a code from the name; the location and currency lists use the standard codes (US, US-TX, USD). A code cannot be changed once created.
• States sit under a country. A state or province belongs to a country you have active; retire the country and you must reactivate it before a state under it can come back.

Use the filter box for the long lists (Country, Currency, State or province), the country filter to work within one country's states, and Show retired to see and reactivate retired entries.

Project field rules

Field rules decide which project profile fields a project must fill in, may fill in, or does not see at all. Each of the profile fields — structured location (country, state or province, city, site name, address, postal code), start and finish dates, market sector, project type, delivery method, currency, and business status — can be set to Required, Optional, or Hidden. Every field starts Optional.

• Required fields must be filled in when a project is created and whenever its profile is saved. An existing project that is missing a newly required field is shown what is missing, but edits to its name, number, client, members, lifecycle and Versions are never blocked by it.
• Hidden fields do not appear on the project profile and do not show on reports (a hidden location part is left out of the composed location line).
• Before you make a field required, the panel shows how many of your current projects have it empty, so you can see who would be prompted.

Editing field rules needs the Standards manager permission, like the dropdown lists, and every change is recorded in the audit trail. A field's rule takes effect immediately.

Governance

Governance sets what projects may do with your company's standards — six settings, each with a plain description of every option. Until you publish a policy, projects run on Jakten's safe defaults, which are the tightest posture.

Governance is not published like branding. It is evaluated live: publishing a policy applies it at once to every non-archived project, not just to new ones. So when a change makes any setting more restrictive, publishing shows exactly which settings tighten, from what to what, and how many projects the change reaches, and asks you to confirm before it takes effect. A loosening change publishes without that step.

• Two settings do something today: whether a project may set its own report cover subtitle, and when a project may refresh its WBS, defaults or branding from the company masters. The panel marks the other four settings as not yet consulted by anything — you can set them, but nothing checks them until a later release wires them.
• "Permitted with approval" is withdrawn. It never had an approval workflow, so it only ever blocked the action. It is no longer offered; if an older policy still shows it, it reads "Permitted with approval (withdrawn — behaves as Disallowed)". Choose Permitted or Disallowed instead.
• Edit the draft, Save draft, then Publish and confirm. Discard draft drops unsaved edits.

9. 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.

10. Subscription and billing

Open Administration → Licensing → Subscription and billing. Company administrators buy and change the subscription here: seats, modules, AI, cancellation, and refund requests. Anyone else who can open Licensing sees the modules, seat counts, and renewal date, with the note To buy seats, add a module or change the subscription, ask your company administrator.

The page shows each subscription your company holds, then the panels Modules and seats, Add a module, AI, Payment methods and invoices, and Refunds. Card details, invoices, and receipts stay with Stripe: the page opens Stripe's billing portal for them.

What you can do, and where

• Seats and modules are changed only on this page. The billing portal does not change them.
• A module keeps at least 1 seat. To stop paying for the subscription, cancel it in the billing portal.
• While a seat reduction is scheduled for renewal, a module cannot be added. Select Keep current seats… on that module first.
• A subscription that is set to end cannot have its seats reduced. Resume it first.
• Each confirmation shows the list price. The exact amount is on the invoice.

Paying in Stripe

Jakten never sees your card details. Buying the AI subscription or a top-up, and every errand in the billing portal, opens Stripe in your web browser, and the page says Stripe opened in your browser. This page updates when you come back.

1. Finish in Stripe, in the browser.
2. Go back to Jakten. The page refreshes itself when its window is back in view; select Refresh to check again at any time.

Added seats and modules are charged to the payment method Stripe has on file, without opening the browser. They appear once Stripe confirms the payment. If your bank asks you to confirm a payment, open the billing portal and complete it there.

Before you buy

Buying needs your company's acceptance of the current Jakten terms. If they are not accepted, the page says so and nothing is bought: an administrator accepts them under Administration → Licensing → Licenses (Legal acceptance), then tries again.

Refunds

The Terms of Service (section 5) give a 14-day guarantee on a first purchase made directly from Jakten.

• What can be refunded. A module's first purchase, in full, if you ask within 14 calendar days. The day of purchase is day 1, so the last day to ask is the 14th. The page shows that date on the purchase's button, Request a refund (window closes …). Days are counted from the date on the invoice, in UTC.
• A module added later to your subscription is its own first purchase, with its own 14 days.
• Never refunded: seats added to a module you already have, and renewals.
• AI. The first AI subscription payment can be refunded within 14 days only if no credits have been used. A top-up can be refunded within 14 days only while none of its credits have been used. Later AI subscription payments are never refunded.
• How to ask. Under Refunds, select Request a refund next to the purchase, give a reason if you like, and select Request refund. Only purchases that can still be refunded are listed; when there are none, the panel says Nothing bought in the last 14 days can be refunded. Each purchase can have one request waiting at a time.
• Jakten reviews every request and emails you the decision. The Requests table on the page shows each request as Waiting for Jakten, Approved; the refund is on its way, Refunded, or Declined.
• If it is approved, what you paid for that module on its first invoice, after any discount, goes back to the payment method that paid it, and the module ends at once: everyone holding a seat in it loses access to that module. Seats you added to the module later end with it, but are not refunded. Other modules are not affected.
• Your last module and AI. If the refunded module is your company's last license for a Jakten module, your AI subscription is set to end at the end of its current month. It does not renew, and the module's refund does not include it. While your company keeps a license for any other module, AI is unaffected.
• If it is declined, the reason shows beside the request in the Requests table. You may ask again while the window is still open.

If more seats are assigned than continue at renewal

A seat reduction takes effect at renewal, and seats can still be assigned until then. When more seats are assigned than will continue, the At renewal column warns you. Before the renewal date, revoke seats under Administration → Licensing → Seats, or select Keep current seats… to cancel the reduction.

If you do neither, the lower count takes effect on the renewal date, and the people assigned most recently beyond the paid count lose access to that module that day. The people with the longest-standing seats, up to the paid count, keep working. The same applies whenever the paid count drops below the seats assigned. The people who lost access see a message that the company has more people assigned than it pays for, and that they should ask their company administrator. They can still sign in and use their other modules.

To fix it, open Administration → Licensing → Seats. The page names the people who have lost access in each module and how many seats are over. Then do one of the following:

• Revoke seats from people who no longer need the module. Each seat you revoke gives the next person in line access again at once.
• Buy more seats under Administration → Licensing → Subscription and billing. Access returns once the new seats reach your installation.

No further seats in that module can be assigned until the assignments are within the paid count.

Subscription states

Each subscription's card on the page shows where it stands:

While your yearly subscription is suspended or has ended, the page shows it with a notice and offers only the billing portal: nothing can be bought, changed, or refunded from the page.

Access restrictions. When a payment fails or the license cannot be validated, Administration → Licensing → Licenses shows the operational mode:

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

Emails

• From Stripe: receipts and invoices, sent to the billing email address in the billing portal. Change that address in the billing portal.
• From Jakten: a notice when a refund is requested, approved, or declined, when a cancellation is scheduled, and when a change is scheduled for renewal. These go to your company's billing contact: the contact email given with your company's first purchase. To change it, email [email protected].

When to contact Jakten support

Email [email protected] when:

• The page says Your subscription is managed by Jakten; email [email protected] to change it. This appears when your company has no online billing account, or when this installation is not registered for online billing or cannot read its billing credential.
• The page says your company has more than one yearly subscription. Jakten combines them, and then the page can change them.
• Your subscription has ended and you want to subscribe again.
• Jakten's billing emails should go to a different address.

When the page says that Jakten's billing service can't be reached from this installation, check the connection to licensing.jakten.net first (see Network and Firewall Requirements).

Jakten AI

Jakten AI is a monthly subscription for the whole company, bought beside the module seats. It needs a paid seat in any Jakten module, and what it does follows the modules your company holds:

• Ask Jakten, in every module: answers how-to questions from Jakten's published documentation. It opens from Help and from Ask Jakten in the top bar of each module (see the Platform User Guide, Get help).
• Jakten Quote, with a Quote seat: reads bids, maps bid lines to your WBS, proposes adjustments, analyzes qualifications, drafts the award narrative and the clarification, RFI and BAFO letters, and answers questions about a package's bids.
• Jakten Assurance, with an Assurance seat: suggests column and WBS mappings when an import does not match, answers questions about an estimate Version (Ask the estimate), drafts a metric definition from a description, reads a basis document for its assumptions, exclusions and qualifications, and drafts Basis of Estimate blocks and review slides. A person accepts every suggestion before it changes anything, and a figure in an answer is counted or cited by Assurance, never written by AI.
• Jakten Risk, with a Risk seat: drafts the Full Report's analysis summary from a sealed run (Draft summary), and drafts risk events from the scenario's estimate, the Knowledge Assurance published and the risks Quote's award published (Draft risk events). A person prices and accepts each event; nothing drafted enters a simulation until then.

Without the AI subscription every module is the complete product without AI. AI needs two things: a Jakten AI subscription for the company, and an administrator's opt-in to the *Jakten AI Data Processing Terms*.

Turn AI on or off. Open Administration → Licensing → Subscription and billing. In the AI panel, under AI data processing, select Opt in…, read the terms it links, and confirm. Withdraw… in the same place turns AI off. Opting in needs your company's acceptance of the current Jakten terms and a license in good standing (see Before you buy); withdrawing always works. The opt-in covers the whole company and every Jakten module, and it takes effect at Jakten's gateway, not only on one workstation. If the terms are updated, AI pauses until an administrator opts in to the new version. In Quote, Settings → AI and usage shows company administrators whether your company has opted in, with a link to that page.

Tiers. AI is measured in credits. Each tier grants credits every month and limits how many can be used in one day. The credits are your company's, shared by everyone who uses AI, in every module. Personal tiers are sized for one person working alone and business tiers for teams; either kind can be bought by any company. The price of each tier shows when you choose it under Buy AI subscription….

Enterprise is an annual commitment arranged with Jakten, not bought on the page: email [email protected].

The allowance. The AI panel above shows your tier, the credits remaining, the credits used today, and the renewal date. In Quote, everyone sees whether AI is on and the credits left on the AI chip in the top bar; company administrators see the tier, the credits remaining and the renewal date under Settings → AI and usage.

• Monthly credits reset at each monthly renewal. Unused credits do not carry over.
• The daily limit stops one busy day from spending the month. Days are counted in UTC.
• Top-ups add credits for the rest of the subscription: Small, 17,500 credits, or Large, 60,000 credits, from Buy top-up…. They are used after the month's credits, and do not expire at the end of a month.
• Upgrades take effect immediately; downgrades take effect at the next renewal.
• Credits held while a step runs. Before an AI step runs, Jakten holds enough credits for everything the step sends and the longest answer it could give. When the step finishes, only what it used is charged and the rest is released. Held credits count toward today's limit until then, so a step can be refused a little before the day's actual use reaches the limit. An overnight read, of a Quote bid or an Assurance basis document, holds its credits from when it is sent.

What a credit buys. What a step costs depends on how much it reads and writes. These costs were measured on sample projects; yours vary with the documents and the size of the estimate.

A question usually reuses the documents it draws on, already sent. Ask Jakten sends its documentation again when no question has been asked of it for five minutes; the cost of that question is the higher figure. A question about a package's bids sends the package's documents again when none has been asked about the package for an hour, or when a bid or document in the package has changed. In Assurance, a question about an estimate sends the Version's estimate context, Knowledge and basis documents again when no question has been asked about that Version for an hour, or when any of them has changed; a draft does the same with drafts. An import suggestion costs the figure shown when the sheet's WBS codes need placing, since your WBS is sent with them; when only column headers are unmatched it costs about 19. These Assurance figures were measured on a sample Version with a few short basis documents: a Version with more Knowledge, Basis of Estimate text or basis documents costs more per question, and when its basis documents are too long to send whole, the pages sent depend on the question, so more questions send them again.

Limits are hard stops. Before any AI step runs, Jakten checks it against your company's limits. A step that would go past one does not run. Ask Jakten or the module says why and what is left, and, where an administrator can fix it, Ask your company administrator.

Usage. Select Show usage on the AI panel to see this month's credits by purpose, such as Ask Jakten or reading a bid, and by person. In Quote, a company administrator selects Usage by seat under Settings → AI and usage for Quote's use.

What is kept. Jakten's AI gateway keeps a usage record of each request (your company and installation, the feature, the model, the tokens, the credits, the time, a coded reference to the person, and the AI provider's reference for the request), and the provider's error message when it returns one; never the documents, questions or answers. Quote keeps its suggestions, the decisions on them, and the questions and answers about a package's bids in your company's own database. Assurance keeps its suggestions and drafts, the decisions on them, and the questions and answers about each Version in your company's own database, and Risk keeps its drafted summaries and event proposals and the decisions on them in its own. Ask Jakten keeps nothing: closing it ends the conversation. What the AI provider keeps, and for how long, is in the *Jakten AI Data Processing Terms*.

11. 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.

12. 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.

13. 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