Plans, Seats & Team Access

The approved commercial baseline includes a 14-day trial. Public Pricing CTAs open managed account creation, and this public help page is read-only: it does not collect payment or expose private account data. After selecting a Business, a verified owner can use the private Owner Portal to request a server refresh. When the server confirms no customer or no active/trialing subscription, the owner can start an approved private recurring Checkout session. Enterprise is custom and has no self-serve checkout.

Annual billing uses each plan's fixed annual total. Those totals represent two months free compared with twelve monthly payments. Taxes, setup fees, cancellation terms, and final inclusions still need confirmation.

No. This public help page is read-only. It does not display your private subscription snapshot, collect payment, start checkout, upgrade, downgrade, cancel, refund, or confirm a paid seat. After selecting a Business, a verified Business Owner can use the private Owner Portal to request a server subscription refresh. When the server truthfully confirms no customer or no active/trialing subscription, the owner can start an approved private recurring Checkout session. When the plan match and membership query are trusted, the private readout can show accepted Workspace membership usage, including the owner once. The Owner Portal can also send, review, and revoke pending tokenized invitations for a selected active Workspace after a trusted included-seat check. Pending invitations do not consume a seat. After managed sign-in and production identity setup, an invitee can explicitly accept when the invited email, Business, Workspace, plan, seat allowance, and audit checks pass. Full or unknown allowances block membership creation without a charge. The public page never exposes invitation rows or other account state. Upgrades, downgrades, cancellations, refunds, renewal lifecycle management, paid-seat confirmation or activation, Customer Portal access, and member offboarding remain deferred.

A seat is one person with authenticated access to the TaskPulse account. One person should use one login so access and future audit history stay attributable.

The baseline is Starter 1, Professional 3, Business 5, Executive 10, Enterprise Custom. These are public plan rules, not private account state. The Owner Portal can show accepted Workspace membership usage only after it safely resolves both the plan and the membership source.

Yes. A verified Business Owner can privately send, review, and revoke a tokenized invitation for a selected active Workspace after TaskPulse confirms an exact plan and trusted included-seat allowance. Pending invitations do not consume a seat. After managed sign-in and normal production identity setup, the invitee can explicitly accept when TaskPulse confirms the invited email, active Business and Workspace, exact plan, trusted seat allowance, and audit checks. Full or unknown allowances block membership creation without a charge. This public Help page shows no private invitation rows or account-specific counts.

The approved baseline is $12 per additional user per month. It is a planning rule in this slice, not a charge or a current account quote.

No. Those are relationship records. A saved contact or customer email does not create an authenticated member, invitation, role, workspace membership, or billable seat.

No. A seat describes authenticated access for a person. A role describes that person's responsibilities and permission boundary after access exists.

The owner should assign a role deliberately, and the system should enforce capabilities within the right Business, Workspace, Office, and authority boundaries. A role should never be inferred from an email address alone.

No. Current Workforce records are owner-managed responsibility records. They do not create login accounts, invitations, authenticated membership, billable seats, or authority grants.

No. Temporary Access is a bounded preview grant. It is separate from a permanent member account and does not create a paid seat, Workforce record, invitation, or production authority.

The current foundation stores a server-derived expiration for each grant. The owner chooses from the available bounded durations, and the server enforces expiration when the grant is refreshed or used.

Yes, the current grant foundation supports owner-controlled revocation and retains the audit record. A revoked grant cannot be reused as a permanent account or seat.

Individual logins make responsibility clear. They help an owner understand who had access, which role applied, and when an access decision changed. Shared credentials make that history unreliable.

A live member flow should stop that person's authenticated access, preserve relevant business records, and retain an audit trail for the invitation, role, seat, and removal decisions. That workflow is not connected in this slice.

The existing private Workforce and Temporary Preview foundations keep their current server-side boundaries and audit behavior. A verified Business Owner can also request a private server subscription refresh for a selected Business in the Owner Portal. When that refresh truthfully confirms no customer or no active/trialing subscription, the owner can start an approved private recurring Checkout session. When trusted, that private snapshot counts the verified owner and accepted Workspace members only. The Owner Portal can send, review, and revoke pending tokenized invitations for a selected active Workspace, and pending invitations do not consume seats. After managed sign-in and production identity setup, an invitee can explicitly accept when the invited email, Business, Workspace, plan, seat allowance, and audit checks pass. This public page never shows the private count or invitation rows. Upgrades, downgrades, cancellations, refunds, renewal lifecycle management, paid-seat confirmation or activation, Customer Portal access, and member offboarding remain deferred here.