Read the full walkthrough
1. A workspace for every team
Create your organization
Bring projects into a workspace for your team, your company or a client.
Keep contexts separate
Each organization has its own members, projects, services and permissions. Access to one does not grant access to another.
Switch between workspaces
Use the workspace switcher to find the right context without mixing information between clients.
2. Users and roles
Invite the right people
Invite colleagues by email and choose their organization role: owner, administrator or member.
Invite your collaborators
Invite teammates and assign their roles. A person in several of your workspaces counts only once toward your plan.
Separate roles from permissions
Reading a project, writing documents and approving changes are separate capabilities. Permissions are checked by the server.
3. From a project to its first documents
Give the work a home
Create a project and name its goal. Documentation, resources and contributions will come together in one place.
Choose a project type
Templates guide the documents you need: software product, client work, research and other uses. You can also create custom documents.
Start with a structure
The project receives the template’s documents and rules. Its document language is independent of your interface language.
4. A method agents can follow
Define what belongs where
Each document defines its purpose, what belongs elsewhere and the events that should trigger an update.
Define the expected format
Add writing instructions and a Markdown template: sections, sources to cite and facts to distinguish from assumptions.
Evolve your writing rules
Versioned templates prepare future projects. Existing projects keep their own rules, editable in Documentation method.
5. Readable, traceable project memory
Find the right files
Titles provide context; filenames stay visible. Markdown links connect documents within the project.
Bring in your knowledge
Write, create a document with its definition or import Markdown or text. Changes follow their applicable review process.
Keep the history
Inspect revisions and transactions to understand what changed and find the available rationale.
6. Services connected to real work
Reference your providers
A service represents a provider account, such as your hosting or email platform.
Describe connections
Connections distinguish a service’s uses or environments. The provider account and the credential are separate objects.
Link to the right project
Link the services used by a project. Your team can find its dependencies and explicitly attached credentials.
7. Protected secrets, explicit permissions
Keep credentials in the vault
Add a credential and link it to the relevant project. Lists show its reference and version without exposing its value.
Encrypt stored data
Values are stored in S3 with encryption protected by KMS. This is server-side encryption, not end-to-end encryption.
Keep capabilities separate
Seeing a reference, using a credential through the broker and revealing or exporting its value require separate rights. No system is invulnerable.
8. Connect your external agent
Give your agent one address
Give https://fileaify.com/agent to the agent you work with. It discovers the protocol and requests pairing.
Choose the scope yourself
The agent gives you a link and code. An owner or administrator verifies the request and chooses the workspace, project, capabilities and duration.
Delegate without opening everything
The agent receives its own scoped access. Pairing gives it neither your personal session nor a vault credential.
9. A credential request, a human decision
The agent explains its need
For an additional resource, the agent requests a specific capability with a reason, duration and usage count when needed.
An authorized person decides
An owner or administrator accepts or declines the request. The link presented by the agent brings the decision back to you.
The grant leaves a record
Granted access is documented with its rationale. A document mention never grants a right; missing coverage is flagged.
10. The agent acts, Fileaify keeps the context
Read before working
The agent reads the documents and versioned contract. It knows the rules, decisions and resources it is allowed to see.
Use only the intended access
The HTTPS broker can use a credential without giving it to the agent, against an exact approved destination. Export requires a separate grant.
Report facts and evidence
The agent does operational work in its tools, reports blockers to you and classifies its results into the appropriate documents.
11. Publish with the right level of control
An explicit proposal
The agent submits content, base revisions, the contract used, rationale and evidence. It does not describe an unaccepted proposal as published.
Inspect the changes
By default, an authorized person reviews and accepts or rejects the transaction. The affected documents remain locked while it is pending.
Automate per project
A project can automatically publish contributions from selected agents or all its authorized agents. Permissions, locks and conflicts remain enforced.
12. Collaborate and stay in control
Share lasting project memory
Your team and agents find authorized documents even as people or tools change. Private conversations remain private.
Take decisions with you
Install the remote PWA on your phone from its QR code. Review requests and contributions under the same permission checks.
Revoke future access
Suspend or revoke an agent. Notifications require your permission and a compatible browser. Revocation cannot retrieve a credential already exported.
13. An assistant that finds the context
Ask across authorized projects
The global assistant searches projects you can access. It helps find, explain and summarize information; it cannot modify documents.
Explore in private threads
Keep exchanges in separate threads and attach text, PDFs, DOCX files or images to provide context.
Understand what reaches the AI
Relevant context and attachments are sent to Mistral. Do not paste secrets. Calls are shared by the creator’s workspaces, according to the configured plan quota.
14. A documentation assistant for the project
Plan without changing documents
Inside a project, the assistant is limited to that project. Plan mode helps you understand, prepare a structure and discuss changes.
Ask for reviewable changes
Ask mode prepares changes in a transaction for review. You keep the conversation context and the details of the proposed changes.
Choose autonomy deliberately
In Autonomous mode, transaction review is a separate control. Direct publication requires the right permissions; the assistant does not execute commands or manage access.
15. A regular review, not forgotten knowledge
Schedule project reviews
Enable a periodic review and choose an interval from 1 to 30 days. It is off by default and does not run on every contribution.
Choose what deserves attention
Choose checks: contradictions, freshness, missing documents, open decisions, actions, access, exposed secrets, references, costs and readiness.
Read reports, then decide
Reports remain available in AI Project Review. They flag items to investigate; an AI suggestion is neither evidence nor an automatic correction.
16. Your method stays as your agents evolve
A useful foundation without internal AI
External agents can read and propose contributions on Free, without internal AI. Project, service, secret and member limits depend on the selected plan.
Choose your plan
Solo, Pro and Premium subscriptions are available with real Stripe payments, monthly or annually. Pro and Premium include the Mistral assistant and scheduled reviews, with their quotas. Manage your subscription and invoices in Fileaify Plan in your account.
Start with a real project
Create your workspace, choose a template and invite your team. Then give /agent to your agent: future exchanges will have shared context and explicit rules.