The company app

The company app is the Agreely dashboard, served at app.agreely.ca. It is the surface where an organization manages its consent accountability end to end: it declares what it collects and why, publishes the disclosure its customers will read, issues consent requests, tracks each customer's status, and it is where the organization keeps its Law 25 obligations. It is a workspace for the organization and its privacy officer, not a citizen surface.

The citizen side (the portal where a person reviews an offer, consents with a passkey, and withdraws consent) is a separate application, described in the Citizen portal.

#What the app does

Inside the dashboard, a company:

• Verifies its domain, minting a did:web company identity. Domain verification is the trust anchor: it is what lets consent offers be signed on behalf of the company and verified independently. See Domain and branding.
• Declares its data catalog, the set of catalog items, each a (category, purpose) cell, that describe the personal information it holds and the purposes it holds it for. See The catalog.
• Publishes versioned consent documents (the Forms menu), the disclosure (P-39.1 s. 8; A-2.1 s. 65) a person consents under. See Consent documents.
• Issues consent requests to its customers, as signed, secure deep links. See Consent requests.
• Sees its customers and each one's consent status, at cell granularity. See Customers.
• Runs its Law 25 compliance hub: the person in charge of the protection of personal information, policies, retention, cross-border communication, confidentiality incidents, the rights of the persons concerned, and destruction obligations. See Compliance.
• Keeps a tamper-evident access log: every check decision and every lifecycle event, hash-chained and anchored on-chain. See The access log.
• Opens read-only access to an external reviewer, through a time-boxed, revocable link, with no account. See Auditor access.
• Manages its team, billing, and API keys. See Team and billing.

#Roles and writes

Writes are reserved to the owner and the admin: they are the ones who can declare the catalog, publish a document, issue a request, or edit compliance. A read-only member can view the dashboard without changing it. The separation matters: the actions that commit the organization's accountability stay in authorized hands.

#The onboarding path

At signup, a Guided setup offers five steps, each optional and skippable:

1. Your domain: the organization's domain.
2. Person in charge: the person in charge of the protection of personal information.
3. Signing key: the root passkey that authorizes the company's signing key.
4. DNS record: the TXT record that ties the domain to the company's did:web identity.
5. Invite a teammate.

After that, the Setup page (/setup, opened from the app's launcher, for the owner and admins) lists the steps that get the workspace ready, in the order they are done, in four groups:

• Your workspace: create the workspace, add the domain;
• The register: name the person in charge, define a retention and destruction rule, create a first catalog item;
• Policies and notice: publish the governance policy and the privacy policy, record a privacy impact assessment if you communicate information outside Québec, publish your collection notice;
• Going live: authorize the signing key, publish the DNS record, set up billing, and, optionally, enroll a recovery key or add a backup root passkey.

The steps required before go-live are marked as such. You can come back to any step at any time; the page simply flags what is left to do.

#The menu

The left-hand menu follows the work: Dashboard, Customers, Products and services, then Information and consent (Catalog, Policies, Dissemination, Forms, Requests), then Compliance (Governance, Registers, Accountability, Reference; see Compliance), then Billing and Legal. Settings groups the organization profile, the domain and its verification, the custom domain, the team, the activity log, the root passkey, the API keys and the Export or leave page.

#Where to go next

• The catalog: declaring (category, purpose) cells, the bilingual question, locking, and archiving.
• Consent documents: the disclosure (P-39.1 s. 8; A-2.1 s. 65), immutable versions, and assisted generation.
• Consent requests: issuing an offer to a customer, via the dashboard or the API.
• The access log: the hash-chained register, its anchored epochs and its offline-re-verifiable export.
• Auditor access: the read-only portal and the accountability dossier.
• Citizen portal: what the person concerned sees and does on the other side.
• API reference: issuing and checking programmatically.