Team & Workspace — Krono User Guide | Krono [KRONO](/) Courses [Map your product](/platform/new)[Services](/services)[Guides](/resources)[Pricing](/pricing) About User Guide [Overview](/docs)[Getting started](/docs/getting-started)[How compliance mapping works](/docs/compliance-mapping)[Your documents](/docs/generating-documents)[Tracking certificates, testing & deadlines](/docs/tracking-compliance)[Team & workspace](/docs/team-collaboration)[Pricing & your account](/docs/pricing-and-account) User Guide # Team & workspace A workspace is free and has no member limit. Invite teammates, assign work, and see what everyone's doing across every project in one place — none of it is billed, and none of it is capped. Create one from Settings → Team & Workspace. ## Two levels of roles Roles exist at two different levels, and they answer two different questions: * **Workspace role** (owner, admin, member, or viewer) — what someone can do across your whole organization: invite others, review documents marked final, and manage Krono Team Vault seats if you have them. * **Project role** (owner, editor, or viewer) — what someone can do on one specific project, regardless of their workspace role. A workspace member can be given editor or viewer access to an individual project directly — including someone outside your workspace entirely, like an external auditor, invited as viewer-only on just that one project. ## Unlimited viewer seats, paid editor seats This is the core of how Teams billing works: anyone set to **viewer** — at the workspace level or on an individual project — doesn't count toward your seat count at all, no matter how many viewers you add. You only pay per **editor** seat (someone who uploads documents, checks items off, or manages certificates and tasks). This is deliberate: someone who just needs visibility into where things stand — a manager, a client, an auditor — shouldn't cost you a seat. ## Inviting people Invite a teammate to your whole workspace, or to a single project directly, from that project's `⋯` menu. Choose their role (editor or viewer) when you send the invite — editor seats are billed, viewer seats never are. ## Task assignment and the activity feed Once a project has more than one person on it, you can assign a specific document, test, or certificate to a teammate as a task, and the project's `⋯` menu gains an Activity Feed showing who did what and when — uploads, drafts, status changes, and reviews, in one chronological list, instead of you piecing it together from memory. ## Reviewing a teammate's work A workspace admin (or the project's owner, on a project with no workspace) can approve a submitted document or send it back with a note requesting changes. See [your documents](/docs/generating-documents) for the full document lifecycle this fits into. ## Managing seats and members Everything for managing your workspace lives under Settings → **Team & Workspace** — reachable from the gear icon at the bottom of the platform sidebar, or the account menu in the top navigation bar. Add or remove editor seats there at any time; billing prorates automatically, and there's no seat cap. ## Seeing everything at once The portfolio dashboard (Teams, at `/platform/portfolio`, labeled "All products" in the sidebar) rolls up every project in your workspace into one view — status, at-risk certificates, and overdue tasks — instead of opening each project one at a time to check on it. See [tracking certificates, testing & deadlines](/docs/tracking-compliance) for what feeds into that view. [Krono](/) Courses and books that teach hardware teams EU CE, UK UKCA, US FCC/FDA, and India BIS/CDSCO compliance, plus coverage for Canada, UAE, Hong Kong, Japan, and Australia — with CertifiOS, our compliance platform, and a growing library of guides. Not legal advice. Always consult a qualified professional for product certification decisions. ### Courses * [Browse all courses](/courses) * [Course bundles — 50% off](/bundles) * [CE Marking for Electronics Engineers](/courses/01-ce-marking-for-electronics-engineers) * [FCC Authorization for Hardware Startups](/courses/02-fcc-authorization-for-hardware-startups) ### Books * [Browse all books](/books) ### Platform * [CertifiOS — Free Compliance Roadmap](/platform/new) * [Pricing](/pricing) * [Consulting Services](/services) * [Guides & Resources](/resources) ### Company * [About Krono Labs](/about) * [For Consultants](/for-consultants) * [Trust & Methodology](/trust) * [Docs](/docs) ### Legal * [Privacy Policy](/privacy) * [Terms of Service](/terms) * [contact@krono-labs.com](mailto:contact@krono-labs.com) Supported frameworks REDEMCLVDRoHSMachineryMDRPPEToysFCCUKCAIC RSSISO 13485\+ more © 2026 Krono. All rights reserved. Data sourced from EUR-Lex, European Commission, FCC, legislation.gov.uk, India BIS/CDSCO, and official government publications across all nine markets we cover.