> For the complete documentation index, see [llms.txt](https://help.filed.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.filed.com/guides/getting-started/set-up-your-workspace.md). # Set up your workspace This guide is for the person creating the workspace - typically the firm admin or managing partner. * Teammates joining an existing workspace skip this flow and start from the client hub. Everything configured here can be adjusted later in Settings or Plugins. The onboarding wizard runs once for new workspaces and walks through five screens: firm details, workflow description, AI integration analysis, team invite, and a completion summary. ## Step 1: create your firm The first screen is titled "Welcome to Filed" and collects three things: * **Firm name** (required) - becomes the workspace display name shown across the product. Example placeholder: "Chen & Torres CPA." * **Describe your firm** (optional textarea) - a free-text description of your firm's specialization and location. Example: "We're a CPA firm specialising in small business tax returns and bookkeeping in New York." This description is used to give the AI context about your practice. * **Logo** (optional) - drag-and-drop or click to upload; appears across the workspace. ## Step 2: connect your tools The second screen is titled "Where do you keep your client data?" It contains a single required textarea, **Describe your document storage and workflows**, with an example placeholder: "We use Karbon for client management, store source docs in Google Drive, and file returns through UltraTax. Clients send us documents by email." Describe your firm's tax software, document management system, practice management system, and how clients deliver documents. Filed reads this to determine which integrations to configure. Two CTAs appear: * **Analyze my workflow** submits the description and continues to the next screen. * **Skip for now** skips integration setup; integrations can be configured later from Plugins. ## Step 3: answer the AI follow-up questions Filed's AI picks up the workflow description and asks targeted follow-up questions to confirm which integrations to configure and how to connect them. Expect a short back-and-forth. When the analysis completes, a summary of suggested integrations appears. If the AI gets stuck, a "Try again" option appears alongside "Skip for now," which goes directly to the invite step. ## Step 4: invite your team The invite screen shows your firm name as the heading and "Bring your team on board" as the subtitle. The **Email addresses** field accepts multiple addresses separated by commas, semicolons, or spaces, and each becomes a pill tag. New invites default to the **L1** role, changeable later from Settings > Members. "Send invitations" dispatches invites to all entered addresses. "Skip for now" advances to the completion screen; you can invite teammates at any time from Settings > Members. ## Step 5: your workspace is ready The completion screen is titled "You're ready to start." It shows a three-item recap: * Firm created - with a link to open firm settings * Tools connected (count) - with a link to manage or add integrations in Plugins * Teammates invited (count) - with a link to manage the team "Go to your workspace" navigates to the clients list. If no clients exist yet, the list is empty, which is expected. The next step is [Adding your first client](/guides/getting-started/adding-your-first-client.md). ## What you can change later Nothing set during onboarding is permanent: * **Firm name and logo** - * **Integrations** - Plugins > Integrations (add, edit, or remove at any time) * **Team members** - Settings > Members (invite, change roles, or remove) * **Binder configuration** - Settings > Binder * **SSO** - Settings > SSO --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://help.filed.com/guides/getting-started/set-up-your-workspace.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.