Help center

Two ways in. You can sign up yourself and start learning on the public catalog. Or your employer or institution provisions an account for you, and an invitation email lets you set your own password on first sign-in.

Invitation links expire, and each one works once. Ask the administrator who invited you to send a fresh invitation; they can do that from the members screen of your workspace. If you already accepted an earlier invitation, sign in normally instead and use “Forgot password” if you never set one.

Use the language toggle in the top bar. fkra is built bilingual, not translated: the whole interface flips to right-to-left in Arabic, and content shows its Arabic version when one exists. Your choice is remembered on your next visit.

A current version of Chrome, Edge, Safari, or Firefox, and a network connection. fkra runs in the browser on desktop, tablet, and phone. There is nothing to install.

Choose “Forgot password” on the sign-in screen and we email you a reset link. The link is single-use and short-lived; request another if it expires. If the email does not arrive within a few minutes, check your spam folder and confirm you are using the address your account was created with.

Yes. Two-factor authentication lives in your security settings, with backup codes you can regenerate. If an administrator resets yours, you are prompted to set it up again the next time you sign in.

Profile settings hold your name, photo, title, and language preference. Email changes need verification of the new address. In some workspaces the administrator manages the name and email centrally, so those fields may be read-only for you.

Write to support@fkra.ai from the address on the account and we act on the request. If your account belongs to an employer or institution, that organization controls it. Talk to your administrator, since closing it also affects the records they hold about your learning.

Discover is the front door: browse by domain, by skill, or by learning path. Anything your organization assigns to you also waits on your overview, so you can start there and let the assignment set the order.

Progress records itself as you move: modules you complete, assessment attempts and scores, and the skills those results evidence. It saves continuously, so you can leave mid-lesson and resume where you stopped on any device.

That depends on how the assessment was configured: attempt limits, passing score, and whether answers are shown afterwards are all set by whoever built it. The assessment screen states its own rules before you start.

When a path or certification is set up to issue one, yes. It appears in your certificates and carries a verification link anyone can check. Not every path issues a certificate; the path page says so up front.

Invite people from the members screen, one at a time or in bulk, and give each a role. Invitees set their own password, so you never handle credentials. Roles and permissions are editable afterwards, including access that expires on a date you set.

That is the intended starting point. Bring your documents, slides, video, and audio, and the studio drafts modules, assessments, and media chapters from them. Your authors then review and edit before anything publishes. Nothing goes live because a model produced it.

Enrollment and completion, assessment results, skill coverage, and the activity behind them, as dashboards and as exports. What each administrator sees is bounded by their role, and administrative actions are written to an audit log with the responsible identity attached.

Yes. Managed cloud, a dedicated single-tenant deployment, and on-premise are all supported, as is white-labeling the platform under your own brand. The company page lays out the models, and we would rather talk it through than sell it from a table.

Two copilots, aimed at different work. The learning copilot answers questions inside the lesson you are on, grounded in that material. The authoring copilot drafts modules, assessments, transcripts, chapters, and checkpoints from source material you bring.

No. Your content is processed to produce the output you asked for and nothing else; we do not train or fine-tune models on it. Requests go to AI providers under data processing agreements, carrying only the data the operation needs, and never your credentials.

Yes, and the product is built on that assumption. Generated learning content is a draft until a human reviews and publishes it. Copilot answers point back at the material they came from, so you can check them. Treat both as a fast first pass, not a final authority.

Yes. AI features are configurable per workspace, and an administrator can restrict or disable them. If your policy requires that, tell us during setup and we configure the workspace that way from the start.

You, and the administrators of the workspace your account belongs to, bounded by their role. Each organization’s workspace is segregated from every other, so nobody outside yours sees your activity. We do not sell personal information.

On the managed cloud, in the region agreed for your deployment; data in transit is protected with TLS and sensitive data at rest is encrypted. Dedicated and on-premise deployments put the data wherever your policy requires. The privacy policy has the full account.

Yes. Administrators export learner records, results, and audit trails from the reporting screens. For a personal copy of your own data, or a deletion request, write to support@fkra.ai and we handle it under the rights described in the privacy policy.

A small set of essential first-party cookies: one to keep you signed in, and ones that remember your language and theme. No advertising cookies, no third-party analytics. The cookie policy names each one.