FAQ

Start on the sign-up screen with an email and password or a Google account. After signing up, create an organization Workspace or accept an invite you received. During the launch preparation period, only approved organizations and invited accounts can use Workspace, and if that doesn't apply to you, the screen tells you so.

An organization owner or admin invites them by email from the admin screen. Invitees open the link in the invite email and must sign in with the invited email account.

Sign in with your existing password, then check the Google account connection. We don't link accounts automatically just because the email address matches. Don't keep creating new accounts; contact us through the support guide.

Request deletion from your account email to contact@crewon.ai. The support team checks account ownership, organization data and the legal retention scope, then explains what will be processed. We never ask for passwords or verification codes.

Mail, Messenger, video meetings, Calendar, Drive, Notes, Tasks, Approval and more are available, and AgentHub, Workflow, the admin console and the iOS app are in beta. Services such as Knowledge, Project and Sales are in preparation and will be added in turn.

On the pricing page you can compare who each plan is for and its main limits. Free is free, and Standard and Business, whose prices aren't published yet, show "to be decided" instead of a price. Enterprise is offered through a separate consultation and quote.

The launch pricing policy separates individual and organization subscriptions. An organization shares one plan, and users in the same organization can't each choose a different plan. Check the sign-up and payment screens for whether subscriptions have actually started.

Accounting, TradeFlow and Forge are subscribed to separately by service after a trial. Trial periods and separate subscription prices will be announced once set.

Payment for paid plans isn't open yet. Payment methods, billing cycles and how tax invoices (Korea) are issued will be explained on the pricing page and this page when paid payment starts. If you need a paid adoption before then, contact us through Talk to sales.

Refund criteria will be published in the terms of service and refund policy before paid payment starts. No payments are made before then.

An AI colleague placed in your company that works within its role and allowed tools. When information is missing it asks people, and work that affects the outside can stop at a human approval point.

Share the work context and the result you want, then check what the Crew proposes or produces and its evidence. Keep going together by pointing out what to fix or asking for follow-up work. What you can assign depends on the Crew's role, connected services and allowed permissions.

An organization admin finds AI Crew on the AgentHub hiring screen, checks what it does and the tools it uses, then hires it. A hired AI Crew is placed on a team with a set role and permissions. Terms of use for each AI Crew are shown on the hiring screen.

Under the launch policy, every user is assigned an assistant AI Crew, with add-on token products beyond the base tokens. Role-specific AI Crew other than assistants use a separate plan. Base token amounts and add-on terms will be announced once calculated and set.

No. AI Crew does allowed work such as lookups and preparing drafts, and high-impact work such as sending outside or approvals follows policy and human approval boundaries. The system blocks AI Crew from completing approvals on its own, and only people can make payments.

It works only within delegated scope, not with the full permissions of a person's account. It acts within the files and tools tied to the assigned work, with permissions that record who it acts for.

Work is split into five levels by impact. AI Crew goes ahead with reading, and reports after doing reversible work. People approve each action that affects the outside, such as sending email or messages, and handle orders, payment and approvals themselves. AI Crew doesn't change account or security settings or delete anything. Admins and users can only make the standards stricter.

Memory is stored separately for each organization, and it remembers only sources the organization allows. In the Memory tab you can see what it remembered and remove or delete it, and removed memories can be restored within 30 days.

Results from expert AI Crew are reference material, and people make the final call. Check the evidence presented with the results, then the responsible person decides whether to apply them.

No. The server enforces each organization's data and permission boundaries. Seeing a name in the organization directory doesn't by itself grant access to data.

The stored connection credentials are revoked and syncing stops. Data already synced is deleted according to an account deletion request or the retention policy.

For important changes, we publish the new version and its effective date before it takes effect, and keep earlier versions available in the change history.

Company name, contact name, company email and optional fields are used only for receiving the request and following up, and are kept for up to 2 years while the consultation is ongoing and 90 days after it ends.

We don't sell personal data. We don't share it with independent third parties except when required by law, at a user's request or when needed to provide the service.

People's accounts sign in through a central identity provider and authentication service. Signing out deletes the session cookie and invalidates the session.

Requests, progress, approvals and results are kept as activity records so you can check them later.

Every connection is protected with TLS, and secrets on the server are stored encrypted.

We don't publish unverified security certification badges or availability figures. Dedicated audit record storage and a high-availability multi-server setup are in preparation.

Send the impact and reproduction conditions to contact@crewon.ai. Don't access or change real user data, and don't send verification codes or passwords.

Tell us your organization's size, the services you need and whether you want SaaS or on-premises through Talk to sales. For on-premises, the scope, data location and operating responsibility are set in the adoption contract.

With SaaS, you start as soon as you create an organization, and crewai.work handles updates and operations. On-premises is installed directly in your infrastructure or closed network, and data, activity records and logs stay with you. Both are offered from the same product code.

It links to existing company accounts (AD · SSO). For the AI Crew connection, you can choose an external connection, an in-house install or running without a connection.

It's quoted based on adoption scope and scale. It consists of adoption consulting, the Crewon.ai build, the crewai.work build and existing system integration development where needed, and AI Crew subscriptions.

In the consultation, we sort out the real work and approval method, then create a workspace and set up members and roles. You try an assistant AI Crew first to see the effect, then expand the services and AI Crew you need, team by team.

We're recruiting partners to build and run it together in customer infrastructure and separated networks. You can apply on the partner page.

An early run that invites organizations to try real work with AI Crew first. We review pre-registrations and invite approved organizations in turn during November 2026.

We review willingness to apply it to real work, repetitive work to assign to AI Crew, a feedback contact to share opinions and whether data and security requirements can be shared.

The beta's terms of use and schedule come with the approval notice. Payment for paid plans isn't open yet.

Open the approved organization's workspace and start with the assistant AI Crew. Beta and in-preparation features may change in behavior and screens.