> ## Documentation Index > Fetch the complete documentation index at: https://docs.letsflow.ai/llms.txt > Use this file to discover all available pages before exploring further. # Common questions > Answers about getting started, helping employees, building automations, and keeping work under control. ## About Flow ### What is Flow? Flow is a conversational service desk from ServiceNow. Employees ask for help in the channels they already use. Flow answers from your connected knowledge, handles requests, and runs automations your team publishes. Operators manage the work in [Conversations](/setup/conversations). ### Who is Flow for? Flow supports teams that provide services to employees, including IT, HR, Finance, Legal, and Facilities. Start with one team and a common request, such as application access. Add more teams and services as you grow. See [Set up your workspace](/setup/admin-onboarding). ### Do I need an existing ServiceNow instance? No. ServiceNow builds and supports Flow as a standalone product. Flow has its own help desk for receiving requests, assigning work, collecting approvals, and resolving requests. See [Help desk](/setup/help-desk). ### Can I keep my current service desk? Yes. Flow supports ticket sync with ServiceNow and Jira Service Management. You choose which records and updates sync through the connection's mappings. Employees can request help through Flow while your team continues using its existing service desk. See [Ticketing integrations](/integrations/ticketing/overview). ## Getting started ### What do I need to set up first? Start with one team, one requester channel, and the connections needed for its first service. Invite the people who will manage requests. Connect your knowledge, publish a service, and test a request from start to finish before inviting more employees. Follow [Set up your workspace](/setup/admin-onboarding). ### Where can employees ask for help? Employees can use Slack or Microsoft Teams, based on your organization's connected chat provider, and email. They describe what they need and continue in the same conversation. People with browser access can also ask Flow questions from **Home**. See [Channels](/setup/channels/overview). Employees can also use an AI assistant connected to Flow through Model Context Protocol (MCP) to check request progress. When your organization enables request submission through MCP, they can submit requests from the assistant too. Their Flow permissions still apply. See [Connect an AI assistant](/setup/mcp). ### Does every employee need a Flow browser account? No. Employees can request help through connected chat channels without a browser invitation. Invite operators and administrators who need to manage work in Flow. For email from new requesters, connect Directory Sync first. See [End user](/setup/end-user) and [Email prerequisites](/setup/channels/email). ### Do we need single sign-on or Directory Sync to start? Both are optional for an initial chat rollout. Single sign-on (SSO) connects work-account sign-in. Directory Sync adds employee information, manager relationships, and group membership. Connect it when you need those details for approvals or access, or to accept email from new requesters. See [Identity and directory](/setup/administration/identity-and-directory). ## Helping employees ### Can Flow use the knowledge we already have? Yes. Connect sources such as SharePoint, Confluence, Google Drive, and ServiceNow Knowledge Base. Choose the content to sync, then check that the first sync completes. Flow can use that content to answer questions and link employees to the original documents. See [Knowledge](/setup/knowledge). ### Who can see answers from our knowledge sources? Flow checks access before using connected knowledge in an answer. Depending on the source and setup, access follows source permissions or an administrator's selected audience. Choose the sharing settings when connecting each source. See [Knowledge integrations](/integrations/knowledge/overview) for each provider's options. ### What happens when a request needs a person? Operators work the request in **Conversations**. They can read its history, assign it to the right person or team, reply to the requester, and resolve it when the work is complete. Approval requests go to eligible approvers. See [Help desk](/setup/help-desk) and [Approvals](/setup/approvals). ### Can we tailor Flow's answers to our organization? Yes. Publish organization or team instructions to guide Flow's language and handling of requests. For example, tell Flow which information to collect before escalating a facilities request. Instructions work alongside your connected knowledge, permissions, and approvals. See [Configure Flow instructions](/setup/knowledge#configure-flow-instructions). ## Building and running automations ### Do I need to write code to build an automation? You can start by describing the work in plain language. Flow generates an automation for you to review and test before publishing. For example, ask it to send your support team a weekday summary of urgent requests. See [Build your first automation](/automations/build/first-automation). ### Who can build automations? Team **Creators**, **Managers**, and organization administrators can build automations when the team has automations enabled. Publishing lets you choose who can request or run the automation and which connections it can use. See [Permissions](/setup/permissions) and [Publish and execution scope](/automations/build/publish-and-execution-scope). ### Can an automation run without someone asking Flow? Yes. Use a schedule for recurring work or an event for work that starts when something changes. For example, send a daily request summary or alert support when a request becomes urgent. See [Schedule and event examples](/automations/trigger#run-work-without-a-new-request). ### Can we require approval before an action runs? Yes. Add approval steps for work that needs a decision, such as granting application access. The automation waits for the required decision before continuing. Review the generated steps and test the approval path before publishing. See [Inputs and approvals](/automations/build/inputs-and-approvals). ### Which applications can automations work with? Flow provides integrations for tasks such as managing accounts, creating service-desk requests, and sending messages. Each integration lists its supported actions and required permissions. Choose the connections your automation needs when testing and publishing. Browse [Automation integrations](/automations/connectors). ## Security, results, and support ### How does Flow protect our data? Flow encrypts data in transit and at rest. Organization and team roles control access to work, and permission and approval checks apply to AI actions. Uploaded and imported files undergo malware checks before use. See [Product security](/setup/security), including the security data sheet for your review team. ### Can we see who changed something or approved a request? Yes. Administrators can review security and administrative activity in the audit trail, including permission changes and approvals. For automation work, run history shows the steps and outcomes. See [Audit and API access](/setup/administration/audit-and-api-access) and [Monitor automations](/automations/monitor). ### How can we measure whether Flow is helping? Open **Analytics → Dashboard** to track request volume, AI deflection, automation success, and human time to resolve. Choose a reporting period and team to compare results over time. The [Analytics guide](/setup/analytics) explains each measure with examples. ### Where can I get help with Flow? Use **Feedback** in the Flow sidebar to report a product problem. Include what happened, what you expected, and the affected conversation or automation run when available. For account or commercial questions, use your organization's Flow support channel. See [Support](/setup/support). This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.