# Welcome to Appmint: create your organization and complete your first setup

Appmint connects the work of running a business—customers, sales, communication, content and operations—with the tools for building its websites and applications. Your organization is the starting point: it identifies the business you sign into and work on.

This walkthrough follows the screens in the order you encounter them: **signup → welcome page → Studio Manager introduction → organization profile → site and setup controls**. It explains the information to enter, the components introduced after signup, and where to enter your business information. The screenshots come from an account created for this walkthrough. Choose your own available name and enter your own details.

[1. Signup](#1-sign-up-and-enter-your-information) · [2. Welcome page and Appmint components](#2-the-welcome-page-understand-what-you-have-created) · [3. Enter Studio Manager](#3-open-studio-manager-and-acknowledge-the-tour) · [4. Your business information](#4-enter-your-business-information-in-account-profile) · [5. Your site and next setup actions](#5-return-to-home-and-check-your-site) · [6. Help and requests](#6-documentation-support-and-requests)

## 1. Sign up and enter your information

Open [appmint.io](https://appmint.io/) and select **Start free** in the upper-right navigation. This walkthrough uses email signup on the free plan.

### Screen one: Create your account

![Create your account with the email field completed and Continue with Email below it.](assets/onboarding/01-email.png)

Enter your email in **Email**, then select **Continue with Email**. Use the address you intend to use to access Appmint. The **Continue with Google** and **Continue with GitHub** buttons are alternative account routes; the following screens follow the email route.

The next screen is **Finish your account**. This is where you enter your chosen address, your name and your password.

### Screen two: Finish your account

![The empty Finish your account form, showing exactly where the site name, first name, last name, password and confirmation are entered.](assets/onboarding/02-account-fields-empty.png)

**Start with the address field.** Enter your preferred name in **site-name**, to the left of `.appmint.app`. Appmint supplies that suffix, so enter only the name. You may use any available name; it does not have to match your company’s display name. Move to the next field and wait for the availability check. A green message ending **is available** confirms the selected name is available. If it is taken, change the name and check again.

**Enter the owner’s name.** Put your first name in **First name** and your surname in **Last name**, in the two fields immediately below the address. These are your personal account details. The separate **Organization Name** field for your business is in Studio Manager’s Account Profile; we will complete it after the tour.

**Set your password.** Enter a unique password in **Password**, then enter the same value in **Confirm password**. Save it in your password manager. The inputs conceal the characters as you type.

![The same form completed, including the green address-availability result.](assets/onboarding/03-account-fields-complete.png)

Before submitting, review the address and your name. Select **Create account** once and allow the request to finish. If the form reports an issue, correct the indicated field before submitting again. In the completed free signup shown here, Appmint went directly to the welcome page; no email-confirmation screen appeared.

**What you have entered so far:** your login email, chosen address name, personal first and last name, and password. Business display name, logo, interests, locations and team access are later setup items; they are not fields on this signup screen.

## 2. The welcome page: understand what you have created

The welcome page greets you by first name and displays your new organization. Stay on this page while reviewing the sections below. It contains both the entry points into Appmint and the details you will need to return.

![The successful signup welcome, with the Studio Manager and Vibe Studio entry points and account details.](assets/onboarding/04-welcome-top.png)

### Run your business: Studio Manager

The main card is **Run your business**, with **Open Studio Manager**. Studio Manager is the business console: you use it to manage customers, orders, payments, content, settings and your team. It also contains Build Studio and the other management areas introduced in the tour below.

For a business owner, it is the place to oversee and operate the organization. For a developer, it provides the administrative interface for the organization, its data, sites and configuration. **This walkthrough continues in Studio Manager after reviewing the rest of the welcome page.**

### Build pages and applications: Vibe Studio

The next entry is **Building pages or apps? Open Vibe Studio**. Vibe Studio is Appmint’s AI-assisted building environment for pages, tools and applications.

Use the **same production Appmint account** for Vibe Studio and Studio Manager. You do not need another account for each application.

1. Open **Building pages or apps? Open Vibe Studio** from the welcome page, or visit [Vibe Studio](https://vibe-studio.appmint.io/login).
2. If prompted, enter the email used for your Appmint signup and select **Continue with Password**.
3. Enter your organization ID in **Site Name**, enter the same password, and select **Sign In**. The `.appmint.app` suffix is already displayed beside Site Name.
4. Vibe Studio opens its **Start** screen, headed **Build your ideas with Vibe**.

![Vibe Studio Start screen after signing in with the newly created production Appmint account.](assets/onboarding/prod-vibe-first-screen.png)

The central **Describe your idea…** field is where you describe the page or application you want to build. Its **Build** action starts that workflow. Below it, **Start from a template** offers examples such as SaaS Landing Page, Creative Portfolio, Restaurant & Dining, and E-Commerce Store.

The left navigation contains **Start**, **Gallery**, **Dev Environments**, and **FAQ**, with **Support** near the bottom. The new account displays **No dev environments yet**—you have signed in, but have not created a development environment or built a project.

This is the actual signed-in screen captured from production. For the organization setup in this guide, return to Studio Manager using the same account; you can come back to Vibe Studio when you are ready to build.

There are two builder names you will encounter:

- **Vibe Studio** is the building environment opened from this welcome-page link.
- **Build Studio** is the visual builder inside Studio Manager. Its navigation includes new pages, saved pages, templates, forms, presentations and graphics.

Knowing which one a tutorial uses makes its navigation easier to follow. The Studio Manager tour in this guide introduces **Build Studio**; it does not require you to open Vibe Studio or complete a separate project there first.

### Your sign-in details: retain all four items

The **YOUR SIGN-IN DETAILS** section is immediately below the application links.

1. Use **Copy** beside **Sign in at** to retain the management sign-in address. **Open** beside that address opens it.
2. Copy **Organization ID**. Save the exact ID with your login details; it identifies the organization you are accessing.
3. Check the **Email** value against the address you entered during signup.
4. Retain the **Password** in your password manager. The row provides **Show** and **Copy** and explicitly says **Save it now — not shown again**. Leave it concealed when sharing or recording your screen.

The organization ID is not interchangeable with the business’s display name or the name of a selected site. Keep the supplied values rather than reconstructing them from a screenshot or example address.

### The six capability cards: how the business functions connect

Scroll down to the section headed **What your workspace already does**—that is the interface’s wording. The six cards introduce the work your Appmint organization can support.

![All six capability cards on the actual post-signup welcome page.](assets/onboarding/06-welcome-components.png)

**Customers and CRM** is the relationship side of the business: contacts, deals and customer history. This is the context for following a lead, understanding a customer’s previous activity, or giving a colleague the background needed to respond.

**Selling and payments** introduces products, orders, invoices and checkout, both online and in person. An order records the sale; the related customer record and communication provide the surrounding business context.

**Talking to customers** introduces live chat, a shared inbox and broadcasts tied to the same contact records. Use this area when planning how your team will respond to individual enquiries and communicate with groups of customers.

**Your counter and floor** introduces connected hardware such as receipt printers, scanners and card readers. It is relevant to in-person operations. Connecting hardware has its own installation and configuration procedure; the presence of this card does not mean a device has already been connected.

**Finding new business** introduces business and contact discovery, with prospects passed into CRM. It belongs before or alongside your sales follow-up process.

**Pages and apps** introduces the building tools for websites, applications and internal tools, with AI assistance. These tools create the customer-facing or operational interface for the business processes above.

Select a card to open its product information. These are capability introductions, not six mandatory setup tasks or confirmation that every service is configured.

### Where the named Appmint components fit

The welcome page groups capabilities by business purpose. You will also encounter product names in the application and documentation. Their relationship is:

| Component | Its place in Appmint |
| --- | --- |
| **Studio Manager** | Business administration and daily operations. |
| **Build Studio** | The visual builder within Studio Manager. |
| **Vibe Studio** | AI-assisted page and application building. |
| **Appmint Mobile** | Mobile access for CRM, POS, payments, scanning and events. |
| **Appmint Chat** | Customer chat, with agent and AI support. |
| **EventOxygen** | Event ticketing, check-in, accreditation and networking. |
| **Device Hub** | Connection to venue hardware such as printers and scanners. |
| **LeadSearch** | Lead capture into CRM from a browser extension. |
| **AppEngine** | The backend/API used by applications and integrations. |

The [Appmint documentation](https://docs.appmint.io/) provides product guides for these components and developer references for AppEngine. They are different ways of working with the platform; signup does not mean you must install or configure every component at once.

### Learn: video, documentation and support

Continue down to **Learn**.

![The welcome page’s Learn section, including the getting-started video, Documentation and Support.](assets/onboarding/07-welcome-learn.png)

The embedded video is titled **VIBE STUDIO WALKTHROUGH** in its player. It introduces that building environment; it is not a recording of the Studio Manager signup and setup steps below. **Documentation** opens the written guides. **Support** opens the support entry, and the footer also includes **Get help**.

Within the documentation, **Products** explains the individual applications; **Developers** covers the backend and integrations; **Tutorials** provides task walkthroughs. Keep these routes available as you move beyond initial setup.

Return to **Run your business** and select **Open Studio Manager**. The rest of this guide follows that application.

## 3. Open Studio Manager and acknowledge the tour

Select **Open Studio Manager** on the welcome page. In the new account, Studio Manager opens with the **Getting around** tour over Home. The first card, **Welcome — let me show you the whole thing**, is marked **1 of 44**.

![Studio Manager’s first-run tour over Home.](assets/onboarding/tour-01.png)

The tour introduces navigation, website tools, content, selling, CRM, automation, billing, data, configuration and help. **Next** advances, **Back** revisits a card, **Skip section** moves to another chapter, and **End** closes the tour. The last card has **Done**.

You can take the tour now or select **End** and continue with the organization setup below. Reopen it any time through **Support → Interface tour**. The [complete illustrated tour reference](appmint-studio-tour.md) covers all 44 stops when you need it.

Before entering your business information, note the three parts of the interface: the **left sidebar** selects an area of work, the **main area** displays that area's page or form, and the **top toolbar** keeps communication and help available. If the sidebar shows icons only, use **Expand sidebar** at its top to reveal the navigation labels.

## 4. Enter your business information in Account Profile

Signup collected the owner’s details and an available address. **Account Profile** is where you enter the organization’s display name and interests and access the logo controls.

Selecting the **Account** name opens its **Account & Security** overview, which groups profile/security, billing/subscription and developer tools such as API keys and usage. To enter the organization’s business information, use the arrow and **Profile** submenu described below.

### Open the organization form

1. Expand the sidebar if it currently shows only icons.
2. Select the small arrow beside **Account** to expand its submenu.
3. Select **Profile** in that submenu. The page opens with the heading **Account Profile** and tabs for **Profile**, **Billing & Credits**, **Subscription**, and **Billing History**.
4. Stay on **Profile** for the information below.

![Account expanded, with Profile visible in its submenu.](assets/onboarding/13-account-expanded.png)

This navigation matters: **Account → Profile** opens the organization form. The separate **Edit Profile** shortcut on Account’s overview opened a different route and returned **User ID is required** during testing. Use the submenu route shown here for organization setup.

### Enter Organization Name

![Account Profile before changes, showing the organization-name field, identity details and interests.](assets/onboarding/14-organization-profile.png)

Enter your business’s display name in **Organization Name**, whose placeholder is **Your organization name**. The form explains that this name appears on public forms, emails and documents. Use the name you intend customers and recipients to recognize.

This field is separate from the signup address and organization ID. In this new account it was initially empty even though the organization ID was already present in **Organization Identity**. Creating the account had not filled in this display name for us.

### Review the logo controls and organization identity

The image area offers **Select** and **Upload**. The Select control is labeled **Pick from File Manager**; Upload is the entry for providing a file. Use your own business logo when completing branding.

**Organization Identity** displays the organization ID, database, account status, active state, email and verified-email information. These identify the account; they are not the organization-name input. **Subscription & Billing** displays the plan and account balance alongside the other billing fields.

### Select your interests and save

Under **Organization Details → Interests**, select the areas relevant to your intended use. The form offers:

- Website, blog, etc; Mobile App; E-Commerce/POS; Learning Management.
- Live Chat & AI Chatbot; Social Media Management; Forms & Survey.
- CRM, Sales, Leads & Ticket Support; Email Marketing; Booking, Event, Reservation.
- Project Management; Analytics & Dashboard; Creative Studio; Process Automation & Workflow.

For this practice account, we entered a training display name and selected **Website, blog, etc** and **CRM, Sales, Leads & Ticket Support**. Choose the values that describe your business. These selections record interests; they are not evidence that a phone service, store or integration has been activated.

![Selected organization interests and the Save Changes button before saving.](assets/onboarding/15-profile-filled.png)

Select **Save Changes** and look for **Profile updated successfully**. The button returns to **No Changes**. After saving, reload the page and verify that **Organization Name** and your interest selections remain. The recording below demonstrates this save-and-reload check on the new organization.

![Organization profile after reloading to check the saved information.](assets/onboarding/17-profile-reloaded.png)

![The saved interests remain selected after reload, with No Changes indicating no unsaved edits.](assets/onboarding/18-profile-interests.png)

[Watch entering the organization name, selecting interests, saving and reloading](assets/onboarding/organization-profile-save.webm).

## 5. Return to Home and check your site

Select **App Root** to return to the organization overview. Check **Company Information**, then locate **Active Site**.

![Home after the guided tour, showing the organization and active site.](assets/onboarding/09-after-tour.png)

Read the selected site name before editing. The site name in the capture is **leasite**; it differs from the organization ID and the display name entered above. Use **View public site** to open the address supplied for the selected site. If you need another site, use **Change Site** first.

The same card provides **Site Config**, a custom-domain field with **Connect**, and **Buy Domain**. Below it, **Site Features** contains the site-level capabilities, including Blog, E-Commerce, Forms, Live Chat, Ticket Support, Reservations, Documentation, Community and Audio Player. Configure the features your site needs through their individual procedures.

**For development work:** Home also contains **Development Environments**, with **Manage All Sites & Dev Envs** and **Create Dev Environment**. These are the entry points for managing that work; signing up or viewing the section does not itself create an environment.

For further business setup, select **Configuration**. Its **System Configuration** overview groups **User Management**, **Roles & Permissions**, **Business Locations**, **General Settings**, **Integration Config**, **Translation**, and **Scripts**. It gives you the next setup areas without mixing them with the personal details from signup or the organization profile you just completed.

![System Configuration overview with access, location, settings and integration entry points.](assets/onboarding/10-configuration.png)

Use **Support → How do I…?** for a guided task, such as inviting your team, setting up locations or building the website. **Support → Documentation**, **Submit Ticket**, and **Live Chat** provide reference material and assistance. The support chat option is separate from enabling **Live Chat** on your customer-facing site.

## 6. Documentation, support and requests

Help stays available while you work. Open **Support** in Studio Manager’s top toolbar to find **Documentation**, **Submit Ticket**, and **Live Chat**. **Report a Bug** is a separate button beside Support.

![Studio Manager’s Support menu, with Documentation, Submit Ticket and Live Chat.](assets/orientation-support.png)

### Read the guides

Select **Support → Documentation**, or **Docs** near the bottom of the expanded sidebar. You can also open [Appmint documentation](https://docs.appmint.io/) directly.

Use **Products** to read about a particular Appmint application, **Tutorials** for task walkthroughs, and **Developers** for AppEngine API and integration references. For guidance on the screen you are using, select **What’s this?**; for a task walkthrough inside the application, use **Support → How do I…?**.

### Follow guidance for a specific task

1. Select **How do I…?** in Home’s **Get started** card, or open it through **Support**.
2. The drawer groups tasks under **Website**, **Selling**, **Customers**, **Messaging**, **Money & Plan**, and **Setup**. Choose the task you intend to perform, such as **Invite my team** or **Check my plan, credits and bills**.
3. For website guidance, select **Build my website**. Its four-step guide begins by pointing to **Get started** on Home.
4. Use **Next** to advance or **End** to close the guide. For direct editor access, select **Build your website** on Home; it opens Build Studio.

![The How do I…? drawer with task-specific guidance.](assets/orientation-task-help.png)

These short guides are separate from the complete 44-stop interface tour, so you can get help with the task at hand without replaying that tour.

### Chat with us or submit a support ticket

Open **Support** in the top toolbar. **Live Chat** is the entry for contacting the Appmint team; the separate **Live Chat** switch under Home → Site Features is for visitors to your own website.

![The open Support menu: choose Live Chat for a conversation or Submit Ticket for a written request.](assets/support/menu.png)

If selecting **Live Chat** closes the menu but no conversation appears, use **Support → Submit Ticket**. That is what happened in this local walkthrough; the ticket form opened successfully.

**To prepare a support ticket:**

1. Open **Support → Submit Ticket**. The **Submit Support Ticket** form appears over your current screen.
2. Enter **Subject**: one sentence that identifies the help you need. For example, **Help planning our customer dashboard**.
3. Review **Priority**. The form initially shows **Medium**. Choose a priority that reflects the effect on your business; explain any blocked work in the description.
4. In **Description**, explain your objective, what you have already tried, and where you need help. Include your organization ID and the relevant screen. In our example, customers need to see their orders and request support, while staff need access to the same history.
5. Use **Attachments** to provide relevant screenshots or logs. Remove passwords, API keys and unrelated customer information first.
6. Review the request, then select **Submit Ticket** when you are ready to send it. **Cancel** closes the form without sending this example.

![An unsent support ticket example with Subject, Priority, Description, Attachments and the submission controls.](assets/support/ticket.png)

*The example above was filled in and cancelled. It shows how to prepare a request; no support ticket was sent during this walkthrough.*

### Report a bug

Use a bug report when a control fails or the result differs from the intended behavior. A clear reproduction lets the team investigate the same action you took.

![The Report a Bug form with a concrete example of an action, expected result and actual result.](assets/support/bug-report.png)

1. Select **Report a Bug** in the top toolbar, beside **Support**.
2. In **Bug Title**, identify the failing action. The example is **Support Live Chat does not open a conversation**.
3. In **Description**, write the steps in order, then the expected and actual results. For example: **On Studio Manager Home, open Support and select Live Chat. I expected a conversation panel; the menu closed and no panel appeared.**
4. Check **Current URL**. This field identifies the affected page; make sure it matches the screen where the issue occurred and does not contain a password or sign-in token.
5. In **Error Details**, copy the visible error text. This field is optional. If nothing appeared, say **No visible error message** rather than guessing a cause.
6. Scroll within the form to **Additional Files** for screenshots or logs. The form also shows **Recent Console Errors** and states that browser, operating system and screen-resolution information will be included automatically.
7. Review the information, then select **Submit Bug Report** to send it. Select **Cancel** to leave without submitting.

*This example was prepared and cancelled; a successful submission has not been verified in this walkthrough.*

If Studio displays **Too many requests from this IP, please try again later**, pause before retrying. If it persists, include the action and exact error text in your report. The message alone does not establish that signup failed.

### Need something Appmint does not have yet?

**Tell us—we’re ready to build it for you at no extra cost.** Contact us through **Support → Live Chat** or **Support → Submit Ticket** and explain the workflow or capability you need.

Describe who will use it, what they need to accomplish, and what the finished result should look like. An example, screenshot or existing process helps us understand the request. The team can then discuss the requirements and delivery with you.

Your account is created, the components and management areas have been introduced, and the organization profile has been entered and checked. Continue with the setup for your first business workflow. For website work, the next lesson is [Build your first business page in Build Studio](appmint-first-page.md).