> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stru.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# File Management

> How Documents, Projects, Uploads, Organization, and the Standards folder work in the Stru AI Files area

## Overview

This guide covers the **Files area** of the Stru AI web app — how your documents, projects, and uploads are organized, how sharing and permissions work, and how the shared Standards folder operates. Agent workflows (chatting with an agent, selecting a project in the chat) are covered in the [ETABS & SAP2000 Agents guide](/platform-guides/etabs-sap2000-agents).

<CardGroup cols={2}>
  <Card title="Documents" icon="file-lines">
    Reports, calc sheets, and exports generated for you
  </Card>

  <Card title="Projects" icon="folder-open">
    Your personal project and review folders, where drawings and reviews live
  </Card>

  <Card title="Uploads" icon="upload">
    Default landing spot for files uploaded outside a project
  </Card>

  <Card title="Organization" icon="building">
    Team-wide project folders and the shared Standards folder
  </Card>
</CardGroup>

You can drag files onto any of these cards to upload straight into them.

***

## The Files Home Screen

<AccordionGroup>
  <Accordion title="What are the sections on the Files home screen?" icon="grid">
    Five entry points:

    * **Documents** — the default home for documents the AI generates for you (reports, calc sheets, exports).
    * **Projects** — your personal project folders. This is where drawings live and reviews run.
    * **Uploads** — the default home for files you upload outside a project.
    * **Organization** *(organization accounts only)* — your organization's shared project folders and the shared Standards folder. Everything here is owned by the organization, not by any one person.
    * **Shared with me** — folders and files other people shared directly with you.
  </Accordion>

  <Accordion title="Someone shared a folder with me — where do I find it?" icon="share">
    Under **Shared with me**. Personal folders and single files that teammates share with you land there, and you'll get a live in-app notification the moment they share. Organization-wide projects don't appear there — those live under **Organization**, since everyone in the org already has them.
  </Accordion>
</AccordionGroup>

***

## Projects: Creating and Organizing Folders

<AccordionGroup>
  <Accordion title="How do I create a new folder?" icon="folder-plus">
    Inside **Projects**, click the **+** button in the top right, type a name, and press Enter.
  </Accordion>

  <Accordion title="Can I nest folders?" icon="folder-tree">
    Yes. Create a folder inside another folder to nest it. The breadcrumb trail at the top lets you jump back to any parent level.
  </Accordion>

  <Accordion title="What can I do from a folder's right-click menu?" icon="list">
    Right-clicking a folder opens: **Manage Access**, **Rename**, **Convert to Plain Folder** / **Convert to Review Project**, **Set as Standards Folder**, and **Delete**.
  </Accordion>

  <Accordion title="What happens when I delete a folder?" icon="trash">
    A confirmation dialog warns that deleting removes the folder and its contents **for everyone who has access** — there's no accidental one-click delete.
  </Accordion>
</AccordionGroup>

***

## Review Projects vs. Plain Folders

<AccordionGroup>
  <Accordion title="What's the difference between a Review Project and a Plain Folder?" icon="scale-balanced">
    New folders are **Review Projects** by default — they show a **Launch Review** button, an **Upload Files** prompt, and a **Reviews** section for tracking review jobs.

    **Plain Folders** are pure storage with no review tools — useful for reference material, archives, or the Standards folder.
  </Accordion>

  <Accordion title="Can I switch a folder from one type to the other?" icon="arrows-rotate">
    Yes. Right-click a folder you own and choose **Convert to Plain Folder** or **Convert to Review Project** — the option reverses either way. Converting never touches the files inside, and past review results stay readable.
  </Accordion>
</AccordionGroup>

***

## Sharing and Permissions (Manage Access)

<AccordionGroup>
  <Accordion title="How do I share a file or folder?" icon="user-plus">
    Right-click it → **Manage Access**. Type a teammate's name or email (organization members auto-suggest as you type), pick a role, and click **Add**. Changes apply the moment you click — there's no separate save step.
  </Accordion>

  <Accordion title="What do the Viewer / Editor / Owner roles mean?" icon="id-badge">
    * **Viewer** — view, preview, and download only.
    * **Editor** — everything a Viewer can do, plus upload, create, rename, move, delete, and launch reviews.
    * **Owner** — everything an Editor can do, plus manage who can see the item, manage members and their roles, delete it, and transfer ownership.
  </Accordion>

  <Accordion title="What do the three visibility levels mean?" icon="lock">
    * **Private** — only you and the people you individually add. Access shared on a parent folder still carries down into it.
    * **Organization** — everyone in your organization gets the default role you set (Viewer or Editor), on top of anyone you add individually. Only available on organization-owned folders.
    * **Restricted** — locked down to only the people you explicitly add. It blocks access inherited from parent folders and organization-wide visibility — use it to wall off a sensitive subfolder inside a shared project.
  </Accordion>

  <Accordion title="What's the practical difference between Private and Restricted?" icon="shield-halved">
    Inheritance. A **Private** folder inside a shared project is still reachable by anyone who can access the project above it. A **Restricted** folder cuts that off — parent-folder access and organization visibility stop at its door; only its own member list gets in.
  </Accordion>

  <Accordion title="Can I share with several people at once?" icon="users">
    Yes. Keep typing in the Add field — each Enter (or comma) adds another person as a chip — then click **Add** once to grant them all the same role.
  </Accordion>

  <Accordion title="Can I share with someone who doesn't have a Stru account yet?" icon="envelope">
    Yes. Add their email as usual and they'll show as **"Invited — gets access when they sign up."** The access activates automatically the moment they create an account with that email. Stru doesn't email them, so let them know yourself and point them at the app.
  </Accordion>

  <Accordion title="How will my teammate know I shared something with them?" icon="bell">
    They get a live in-app notification the moment you share — **"«Your name» shared «folder» with you"** — and the item appears in their **Shared with me**. Removing someone's access is deliberately silent.
  </Accordion>

  <Accordion title="If I remove someone's access, how quickly does it apply?" icon="bolt">
    Immediately. Access is re-checked on the server for every request, so a removed person's very next action is denied — even in an already-open tab.
  </Accordion>

  <Accordion title="What does 'Access also carries down from …' mean?" icon="arrow-down">
    It means the folder also inherits people from a parent folder — anyone with access above it can reach this folder too, unless you set it to Restricted. To change who those inherited people are, manage access on the parent folder itself.
  </Accordion>
</AccordionGroup>

***

## The Organization Area and Standards Folder

<AccordionGroup>
  <Accordion title="What is the Organization area?" icon="building">
    A shared Projects area owned by the organization rather than any one person. Files survive a member leaving — the departed person just loses access, and their files stay. Default visibility on organization-owned folders is organization-wide, and the default member role is Editor.
  </Accordion>

  <Accordion title="What is the Standards folder?" icon="book-open">
    Every organization automatically gets a shared **Standards** folder under **Organization**, marked with a small book badge. Drop in whatever the team should treat as reference material — formatting guides, report boilerplate, checklists, calculation examples. Everyone in the organization can see and maintain it by default.

    When "Formatting standards" is on in the chat (it's on by default), the agent has this folder available as working reference and follows what's in it — see the [ETABS & SAP2000 Agents guide](/platform-guides/etabs-sap2000-agents) for how agents use it.
  </Accordion>

  <Accordion title="Can I use my own folder as a standards folder instead?" icon="folder-open">
    Yes. Right-click any folder you can edit → **Set as Standards Folder**. Your designation wins over the organization default, and the folder gets the book badge. Right-click again to remove the designation — you'll fall back to the org Standards folder if you're an organization member.
  </Accordion>

  <Accordion title="Is my choice of standards folder personal or shared with my team?" icon="user">
    Personal. Designating a folder only changes your own conversations — every teammate keeps their own choice, or the organization default if they never made one. What's shared is the *contents* of a shared folder: if you all point at the org Standards folder, you're all working from the same documents.
  </Accordion>

  <Accordion title="Can these templates be centrally managed and updated?" icon="pen-to-square">
    Yes. There's one copy, owned by the organization. Any Editor updates a standard in place and the whole team sees the new version immediately. There's no formal versioning or approval workflow yet — updates are live edits.
  </Accordion>

  <Accordion title="What happens if my standards folder is deleted or someone unshares it from me?" icon="triangle-exclamation">
    Nothing breaks. Organization members fall back to the org Standards folder; individual accounts fall back to no standards folder. Your designation resumes automatically if access comes back. The same fallback applies if your role on the folder drops to Viewer.
  </Accordion>
</AccordionGroup>

***

## Uploads, Documents, and Shared with Me

<AccordionGroup>
  <Accordion title="What's in Uploads?" icon="upload">
    Every file uploaded outside of a project, with columns for status, size, and modified date. Click a column header to toggle sort order.
  </Accordion>

  <Accordion title="What's in Documents?" icon="file-lines">
    Items generated for you — reports, calc sheets, and exports.
  </Accordion>

  <Accordion title="What's in Shared with Me?" icon="people-arrows">
    Folders and individual files other people have shared directly with you. Organization-wide projects don't appear here, since everyone in the organization already has them under **Organization**.
  </Accordion>
</AccordionGroup>

***

## Working with Files

<AccordionGroup>
  <Accordion title="How do I preview a file?" icon="eye">
    Double-click an image file to open a preview with download, fullscreen, and close controls.
  </Accordion>

  <Accordion title="Can I manage multiple files at once?" icon="check-double">
    Yes. Check the box next to one or more files or folders to reveal a bulk action bar (share and delete) in the top toolbar.
  </Accordion>

  <Accordion title="What actions are available for a single file?" icon="ellipsis">
    Right-click a file for **Manage Access**, **Rename**, **Download**, and **Delete**.
  </Accordion>
</AccordionGroup>

***

## Quick Reference

| Concept              | What it means                                                                        |
| -------------------- | ------------------------------------------------------------------------------------ |
| **Private**          | Only you plus the people you add. Inherits access from parent folders.               |
| **Organization**     | Everyone in the org at a default role, plus anyone you add individually.             |
| **Restricted**       | Only the people you add — no inherited access from parent folders or org visibility. |
| **Review Project**   | Drawings, Launch Review, and a Reviews log. Default folder type.                     |
| **Plain Folder**     | Storage only, no review tools.                                                       |
| **Standards folder** | The shared reference library the agent works from, marked with a book badge.         |

***

## Next Steps

<CardGroup cols={2}>
  <Card title="Agent Guides" icon="robot">
    See how agents use projects and the Standards folder

    [ETABS & SAP2000 Agents](/platform-guides/etabs-sap2000-agents)
  </Card>

  <Card title="Open Files" icon="folder-open">
    Go to your Files area to try it out

    [app.stru.ai](https://app.stru.ai)
  </Card>
</CardGroup>

<Info>
  **Questions?** Email **[bhosh@stru.ai](mailto:bhosh@stru.ai)** or [book a call](https://cal.com/bhosh).
</Info>