Skip to content
Explore featuresProduct / Dashboards

Useful dashboards are part of the product.

People see their own records. You see the work that needs doing. These views use separate permissions in each project.

Open an example dashboard

Forms, orders and memberships have a clear place for the person using them and the person managing them.

Browser examples · this tab only

Your examples, from each side

Submit the form or place an example order, then view the same saved record as a member or owner.

Example project view

Member dashboard

View this tab’s saved examples from the member’s side.

Saved in this tab only

Form receipt

Loading this tab’s examples…

Order receipt

Loading this tab’s examples…

Membership access

The member sees what is available and when access changes.

Explore the member area
Illustrative access · no saved membership
Examples are saved in this tab’s browser session. Switching roles only changes the example view; it does not sign you in. No real account is created, no payment is taken and no email is sent.

One event, two useful views.

The member’s confirmation and the owner’s next step come from the same project workflow. What each person can see depends on their role.

Form receiptResponse inbox

Order receiptFulfillment

Membership accessAccess review

Your Kottoko account is separate.

Purchases of Kottoko, downloads, receipts and Creator seats belong to your Kottoko.com organization. Member and owner records stay in each project you create. Project permissions do not grant Kottoko account rights.

  • Purchase and downloadThe planned purchaser account will hold Kottoko receipts, entitled releases, saved setup choices and download recovery. Purchases and project downloads are not open on this public site.
  • Organization accessPeople, additive roles and Creator seats govern Kottoko.com rights; a project member is not automatically a Creator.
  • Project relationshipCertificates, handover and visible maintenance grants describe the relationship to a project. Its members, content and operations stay local.
Read the setup guide