Permissions, visibility, and platform availability

If a folder is missing or an action isn't where you expect it, that's usually access rather than a bug. Documents and Specs each check a view permission and a management permission, and folder sharing narrows things further.

• View my documents and documents shared with me is the baseline for Documents. An administrator can widen a role to All Documents, or leave it at Only my documents and documents shared with me.
• Manage all documents, add new documents covers uploading, adding folders, moving, renaming, deleting, and changing folder sharing.
• A folder's audience is Only me plus anyone you name, Anyone at [your company] plus any outside people you add, or Anyone with access to [project name].
• A parent folder's broad audience limits how private a child folder can be. Changing a folder's sharing also updates its subfolders and files.
• View specs covers reading published specifications.
• Create, update, or delete specs covers importing, organizing, publishing, unpublishing, and deleting specification content.

Default roles are only a starting point. Your project's own permissions decide what you can actually do, so check with an administrator before assuming something is broken.

Once you have the access, you can reach both Documents and Specs from anywhere. The differences come down to screen size: bigger screens show more columns and give you more room to edit.

• Documents and Specs can be viewed on web and in the native app.
• Documents on native use compact menus for download, link, sharing, move, rename, and selection actions that appear inline on desktop.
• Desktop web shows richer Documents columns, including sharing, modified date, and size.
• Specs adapts its division-and-section navigation to a drawer on smaller screens and in the native app.
• Large desktop layouts provide the clearest Specs editing area. Use desktop web for extensive division or section administration.