> For the complete documentation index, see [llms.txt](https://help.craftsmanplus.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.craftsmanplus.com/navigation/dashboard.md). # Dashboard Start a conversation with INTELLIGENCE, jump back into recent projects, and track how your company is using CRAFTSMAN+. The **Dashboard** is your home in CRAFTSMAN+. It opens with INTELLIGENCE, ready for your next idea, and scrolls down to your recent projects and your company's stats. Click **Dashboard** in the top navigation, or the CRAFTSMAN+ logo, to return here from anywhere. *** ### Ask INTELLIGENCE The top of the Dashboard greets you by name with a prompt box for [CRAFTSMAN INTELLIGENCE](https://help.craftsmanplus.com/intelligence/). Describe what you need, like a new playable, a competitor breakdown, or a look at your performance, and press send. INTELLIGENCE opens full screen with a new chat and gets to work. When your request takes you into a project, the conversation comes with you. #### Prompt Ideas Not sure where to start? Click one of the chips below the prompt box to see example prompts for that area: * **Creative Generation:** build a playable from a description, a URL, or a video ad. * **Creative Strategy:** plan the angle, audience, and messaging for a campaign. * **Concept Ideation:** brainstorm playable concepts and mechanics. * **Analytics Insights:** ask questions about how your playables are performing. * **Design Recommendations:** get feedback on how to improve a design. Clicking a chip opens INTELLIGENCE full screen with a list of example prompts. Click any example to send it. {% hint style="info" %} The Dashboard always starts a new chat. Your earlier conversations are in the chat history on the left of the full-screen view. See [Views](/intelligence/chatbot/views.md) and [History](/intelligence/chatbot/history.md). {% endhint %} To leave the full-screen view, click **Go Back**, or click **Dashboard** or another tab in the top navigation. *** ### Recent Projects Scroll down to see your company's ten most recently updated projects. Click one to open it in the editor. Click **New Project** to start something new. See [Projects](/navigation/projects.md). *** ### Company Stats **Company Stats** shows how your team is using CRAFTSMAN+. Use the **Users** filter to see everyone or one person, and the date range to choose the period. The default is the last 30 days. * **Projects Created**, **Variants Created**, and **Total Exports** count your team's activity in the period. * **Average Playable Scores** shows the average [Project Score](/play/export/project-score.md) of your exported playables, with the **Performance**, **Responsivity**, **Engagement**, and **Best Practices** breakdown. * **Exports** shows which partners your team exports to most. * The **Licenses** card shows how long is left on your company's license, how many users you have, and the **Number of Logins** in the period. #### Templates and Trends * **New Templates** shows the newest templates with a live preview. Click **Use Template** to start a project from one. * **Trending Templates** shows the templates being used most across CRAFTSMAN+, and whether their use is going up or down. Click **Use** to start a project from one. * **Trending Partners** shows the partners being exported to most across CRAFTSMAN+. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.craftsmanplus.com/navigation/dashboard.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.