Assets

Assets are Runnit’s universal file library. Any item of work, including a job, project, or organisation, can have files attached to it. Each file belongs to one collection. A collection can be shared across jobs, projects and organisations, so the same file can appear in more than one workspace.

Choose a file view

File lists start in List view when your browser has no saved preference. Use the view buttons to choose thumbnails, list or detail view. Runnit remembers your choice for later visits in that browser.

What an asset can be

Assets cover both text and binary files:

• Markdown, HTML, JSON, CSV, and plain text
• Images (JPG, PNG, GIF, WebP)
• PDFs, videos, and audio

Each asset records who created it (a team member or an AI agent), an optional description, and metadata, and keeps a full version history.

Updating a file keeps the content of its saved versions available for restore. Retained versions use storage as well as the current file. You can see that usage on the Storage page.

If a save reports that retained file history has reached its limit, the change has not been saved. Contact support before retrying. If the file is too large, reduce its content and try again.

Private files

You need permission to view assets to open a file. A private file also requires you to be its uploader, the owner of a conversation it is attached to, or an owner or admin of the authorising organisation. Finance documents keep their Finance permissions. Reading a file does not give you access to the conversation it came from.

An external agent connected with your ordinary user-generated credential can read the same private file when given its ID. Private files remain out of MCP listings and search; internal sessions limited to a job, client or tool set keep their private-file restriction. See Agent Connectivity.

Linking across jobs, projects, and organisations

Files appear on jobs, projects and organisations through their collections. Saving a file into a different collection creates an independent copy owned by that collection’s organisation. Asking Ru to save the same source into the same folder and name again reuses its saved copy, including files Ru saved automatically. Unrelated files with matching names remain separate.

When Ru generates an image in a project conversation, automatic filing reuses the image already available on the project, so it appears once in Assets. Copies keep their AI creator attribution. Existing duplicate files are not removed automatically. See Image generation.

You can organise and reuse files in several ways:

• Organisation brand assets: store brand guidelines and logos once in the Brand Assets collection and let every job reference them.
• Multi-place deliverables: a strategy document can sit against the job it was produced in, the project delivering it, and the organisation’s knowledge base.
• Client work: agencies can keep their own templates separate from a client organisation’s brand assets while still working across both.
• Brief templates: Markdown files in a client’s Brief Templates collection appear in Brief Builder. Selecting one loads its content into an empty brief editor.

Note

When Brief Builder creates its official draft project, the brief uploads and planning-job collections are linked to that project without duplicating the files. They are available from the project’s Assets tab during review. Older brief activation flows may copy job and AI-agent outputs into project storage; those copies keep a reference to their origin.

Where you’ll find assets

The AssetsViewer is the shared file browser used throughout Runnit. You can open it from:

• Settings > Organisation Library for the organisation’s own files (administrators only). It has two groups plus an All files combined view: AI Library holds what the assistant reads while it works (the AI Directives, Component Builder Docs, and Brief Guidance collections), and Files holds the organisation’s own Brand Assets, Reference Docs, and Brief Templates collections, created automatically on first visit and used when internal projects run against the organisation itself, followed by any collections you add.
• The Files tab on a client’s page for client files. It shows one tab per collection: Brand Assets, Reference Docs, Brief Templates, Brief Guidance, AI Directives, any collections you add, and All Files. You only ever see the collections your own organisation keeps for that client, on every tab including All Files.
• A project’s Assets tab for project-level files.
• A job’s assets, grouped by the team member or agent that created them.

Adding your own collections

The default collections cover most work, but you can add a collection for anything that does not fit them (packaging, photography, a campaign archive). You need asset upload access.

1. Open the client’s Files tab, or Settings > Organisation Library for your own organisation, and choose Add collection.
2. Enter a name and, optionally, a description. The description matters: Ru reads it when deciding where to file something.
3. Choose Add collection. The new collection opens in the list on the left.

Each collection in a library needs its own name. If the name is already taken there, Runnit says so and asks for a different one. The same name in a different client’s library is fine.

Select a collection you added and it shows Rename and Delete next to its name. The default collections cannot be renamed or deleted here. Deleting a collection hides it and its files everywhere in Runnit and Ru stops reading from it. Its name becomes free to use again.

Ru treats an added collection like any other: it can read from it, file uploads into it when you ask, and find it by name from chat.

From the viewer you can:

• Move a file to another collection: open it, choose More actions (the three dots in the preview header), then Move to collection. Search or pick from the list, grouped by the organisation library and each client, project and chat. The file moves to the root of that collection. You need upload access to both collections.

• Browse files grouped by creator, and preview Markdown, HTML, images, JSON, and raw text inline.

• Edit text files in place. Markdown opens in a visual editor with a raw source view; HTML is edited as source with a live rendered preview.

• Upload new text or binary files, and delete files you no longer need.

• Organise files into folders with drag and drop.

• Run semantic search and inspect a file’s tags, folder, summary, and indexing status.

• Roll back to an earlier version from the version timeline.

• Download a creator’s files as a ZIP.

• Comment on the file, and ask Ru to work on it (below).

Comments on a file

Every file has its own comment thread. Open a file in the viewer and choose Comments next to Preview and Raw. Comments work like task and project chat: reply to a comment, mention a teammate with @name to notify them, and the person who uploaded the file hears about new comments automatically. Comment notifications link straight to the file with its comments open. You need permission to view assets to read and post.

If your organisation manages a client’s file, your comments are your organisation’s own thread on that file. The client, and any other agency working with them, do not see it.

Ask Ru about a file

Choose Ask Ru in the file header to open a chat about the file you are looking at. Ru reads the file before answering, so you can ask what it says, have it checked against your brand guidelines, or ask for changes:

• “Tighten the introduction” changes the file in place. The file keeps its name and format and gets a new version, so you can roll back.
• “Summarise this deck” on a PDF, Office document, or image creates a new file beside the original, because those files cannot be rewritten in place.
• If you cannot upload files, Ru answers and advises but does not change anything.

Each file has its own conversation, and coming back to the file restores it.

Let Ru do the work from a comment

Mention @runnit in a file comment and describe what you want, for example “@runnit fix the typos and shorten the second section”. Ru starts working on the file in the background as you, with your permissions, and posts what it did (or why it could not) back into the comment thread. Ru reads the earlier comments for context but only follows the request in your mention.

Note

One request runs per file at a time, and you can have three running across files. If Ru is still working on a file, mention it again once it has replied. You need permission to run AI agents; without it Ru says so in the thread instead of starting.

Editing and converting images

Image assets can be sent straight to the Smart Image Editor from the viewer. In one dialog you can resize or crop, apply a style, make a custom edit, or turn a still image into a short video by choosing the motion prompt, duration, and aspect ratio without leaving the modal.

AI Directives collections

Two special collections hold the markdown playbooks that steer Ru, the Runnit assistant:

• the organisation-wide AI Directives collection in the AI Library group of Settings > Organisation Library, seeded with editable defaults; and
• each client’s AI Directives collection on the client page, whose files override the organisation-wide ones for that client.

They behave like normal collections for browsing and preview, but changing their files requires the Manage AI agents permission, and they are left out of semantic search results. See AI Directives for how the files work.

Generate brand guidelines

Every client, and the organisation itself, has a Brand Assets collection: the brand’s guidelines (tone of voice, identity, and rules) and assets such as logos, which the assistant consults before producing work.

Note

This collection was previously named Brand Guidelines, and before that Brand Strategy. Existing collections with the default name were renamed automatically; genuinely custom names were left alone. The separate Creative collection is no longer created. Empty Creative collections were removed; one that still holds files stays where it was and can be renamed or deleted like any collection you add.

While the collection is empty, a Generate Brand Guidelines button appears on the client page’s Brand Assets tab and in the Organisation Library’s Files group. Choosing it opens a fresh Ru chat grounded on that collection. If that chat is already underway, the button becomes Open Brand Guidelines Chat and returns you to the running conversation instead of starting a second one. Ru follows the brand_guidelines_intake.md directive:

1. It interviews you first: what the brand does, tone adjectives, competitors, and anything else it needs. You can upload PDFs, documents, and images or paste URLs at any point.
2. It saves your uploaded source material permanently into the matching Reference Docs collection, and researches remaining gaps on the web.
3. It generates the full guideline set directly into the Brand Assets collection on screen: brand_identity.md, tone_of_voice.md, brand_guidelines.md, brand_canvas.md, competitive_analysis.md, and social_tags.md. Documents are Markdown by default, or HTML if you ask for rendered pages.

Keep iterating in the same chat: ask for corrections and Ru updates the same files, with every edit versioned. Like every directive, the intake behaviour can be edited or overridden per client with the Manage AI agents permission.

Generating brand assets

When working on a client, users who can manage clients can choose Generate Brand Assets on the client page to have Runnit draft brand materials. The work runs as a background Ru task that follows the brand_asset_generation.md directive, researches the client, and saves the finished documents into the client’s Brand Assets collection. You can watch progress in the Automation Queue. The generated files sit alongside any files you upload manually, giving each client a complete brand library.

Removing a project

Deleting a project (from the Delete Project action in the project header menu) removes it along with its tasks, schedules, and member records in a single step. Files that were only linked to that project are removed too, so nothing is left orphaned behind a deleted project.