Skip to content

Frequently asked questions

Answers about team setup, knowledge publication, project submissions, reviews and access.

Frequently asked questions

Use these answers to resolve common setup and workflow issues quickly.

If you still need help, contact support@xyreka.com.

Why does sign-in ask me to use my original provider?

An account already exists with that email using another sign-in method. Use the original method. Xyreka does not automatically link Google and Microsoft accounts, and self-service account linking is not available.

When do I need to verify my email?

Password accounts and new Microsoft accounts need Xyreka mailbox verification. Follow the email link, then sign in again with the same method. If delivery failed or the link expired, use Resend verification email on the sign-in page.

Can a team use different email providers?

Yes. Create an organisation or informal team and invite each person at their own address. Google, Microsoft and password sign-in identify the person; team membership and area assignments determine access. An email domain does not grant a role.

What happens while my access request is pending?

A pending request does not grant new access or remove existing access. An active organisation licence covers its members; individual Plus/Pro plans remain a pilot fallback for unlicensed organisations. Platform administrators approve access. You can set up your organisation while waiting.

Who approves plan requests?

Xyreka platform administrators review plan requests in the admin area. Your team administrator separately manages project, board and knowledge assignments. A team role does not confer platform administration.

Why is my plan active but I cannot see a project or review?

A subscription alone grants no private content permissions. Ask a team administrator for an explicit assignment to that project or board. My Access lists your current assignments.

Who can publish standards and templates?

An explicitly appointed Knowledge Publisher can release an immutable version. Knowledge Editors can prepare drafts. Team administrators manage these assignments but do not automatically receive publication authority.

What must be saved before submitting?

Complete the required project details and checklist answers, select a scanned architecture document with all required sections, and retain the mandatory guidance. Rework also needs a saved response of at least 20 characters. Only a project Lead can submit. Earlier requests retain their original seven-section requirements.

Can the project see the board's internal discussion?

No. Internal notes remain in the assigned board area. A coordinator can release a separate clarification question to the project. Project responses and exports do not include internal board notes.

Does the pilot support formal approval or document uploads?

The structured workflow supports scanned Word/diagram uploads and explicitly authorised human approval or rejection. Uploads require operator-configured private storage and malware scanning. Organisation SSO, assignable custom roles and conditional approval remain future work. Complete supervised acceptance before treating the pilot as authoritative; submission and AI output are not approval or a compliance guarantee.