Finish Organization Setup
Configure the organization for real use after the account, first location, and initial members exist.
Use this page after you have created the organization, added the first location, and invited any initial team members. The goal is to make the workspace usable for real bookings, payments, reporting, and daily operations.
Recommended order
Review the organization basics first, then configure payments, activate only the extensions you need, and test the workflow with one real booking.
Setup Map
Organization basics
Confirm identity, currency, language, locations, and member defaults.
Payment behavior
Create offline methods and decide which payments should count as verified revenue.
Extensions
Install Stripe, messaging, consent forms, ink registration, or other tools only when your workflow needs them.
First booking
Create a booking and confirm the calendar, client, payment, and reporting flow works.
Before You Start
You should know:
- Which studio location should be used first
- Which team members should have manager or admin access
- Which offline payment methods your studio accepts
- Whether you need Stripe for online payments
- Whether staff payments should require verification before they count as revenue
- Which extensions are needed on day one
Most setup tasks require an Owner, Admin, or Manager role.
1. Review Organization Basics
Confirm the organization identity and the defaults that affect scheduling and reporting.
Check:
- Organization name, company email, language, and currency
- First location name and opening hours
- Member roles, calendar colors, revenue targets, and default locations
- Whether members are assigned to the locations where they work
Default location is a convenience, not an access rule
A member's default location can preselect filters and forms. It does not replace role permissions, location assignment, or capacity setup.
Organization settings
The main organization settings page: branding, communication, date/time formats, payments defaults, opening hours, offline payment methods, and deletion.
Review organization-level defaults and identity.
Locations
Locations represent where work happens. Every booking and consultation is assigned a location for scheduling, reporting, and communication.
Create, edit, and archive studio locations.
Members and invites
Invite members, manage roles and calendar colors, assign locations, and configure revenue targets.
Manage members, roles, location assignments, revenue targets, and invites.
2. Configure Payment Behavior
Set payment behavior before the first real booking is created. This keeps staff from recording payments with missing methods or unclear verification rules.
Create Offline Payment Methods
Go to Settings -> Organization -> Offline Payment Methods.
Create the manual methods your team actually accepts:
- Cash
- Card terminal
- Bank transfer
- Other local methods your studio uses
Keep names short because staff will select these methods while recording payments on bookings.
Choose Payment Settings
Go to Settings -> Organization -> Payment Settings.
Review:
- Default offline payment method: the method pre-selected when staff record an offline payment
- Default tax behavior: the tax value pre-filled when creating payments
- Salary period start day: the day used for salary-period reporting presets
- Auto-verify online payments: whether Stripe payments count as trusted automatically
- Auto-verify offline payments: whether manually recorded payments count as trusted automatically
Only verified payments count as revenue
Recorded payments are saved, but they stay out of revenue insights until they are verified. Many studios auto-verify online Stripe payments and manually verify offline payments.
Offline payment methods
Create and manage the manual payment methods your organization can register (cash, bank transfer, terminal, and more).
Create, classify, and archive manual payment methods.
Payment settings
Organization-level defaults for methods, forms, and verification behavior.
Choose default payment behavior, tax behavior, salary period, and verification defaults.
Payment verification
Recorded vs verified payments, roles, and why revenue can differ from expectations.
Understand which payments count as trusted revenue.
3. Activate Needed Extensions
Go to Extensions in the left navigation.
Install only the tools your organization needs now:
- Stripe Payments for online payment links, deposits, and card payments
- Resend Email or Twilio SMS if TatTool should send messages
- Digital Consent Forms if forms should be attached to bookings
- Ink Registration if you track inks used on bookings
Some extensions work immediately. Others require credentials or account setup before the feature is usable.
Stripe setup and accounts
Install Stripe Payments and connect one or more Stripe accounts using Stripe Connect.
Connect and verify a Stripe account before creating payment requests.
Extensions
Add optional features to your TatTool organization (payments, messaging, consent forms, compliance).
See the available extensions and where each one fits.
Managing extensions
Install, configure, deactivate, and understand what happens to your data.
Install, configure, deactivate, and troubleshoot organization extensions.
4. Test The First Booking Workflow
Create one booking before handing the workspace to the team. This confirms that calendar, client, payment, extension, and reporting behavior is working together.
Go to Calendar, then create a booking by:
- Dragging on the calendar
- Clicking Create
- Pressing
Cmd + I
Choose Booking as the event type, then fill in:
- Date and time
- Location
- Participant or artist
- Client email
- Optional client name and phone number
- Description and price
- Any flow that should run for this booking
Open the booking and check the tabs your studio will use, such as payments, media, consent forms, ink registration, history, and flow logs.
Bookings
Create and manage tattoo appointments with clients, payments, media, and history in one place.
Learn the full booking workflow, including clients, payments, conflicts, media, and booking actions.
Clients
Store a client once (by email) and reuse them across bookings, payments, and communication.
Understand how client records are created and reused across bookings.
5. Add And Verify A Test Payment
Open the booking, then go to the Payments tab.
Use:
- Offline payment when money was received outside TatTool, such as cash, terminal, or bank transfer
- Stripe payment request when you want to send a client an online payment link
If you want to collect a deposit now and the remaining balance later, create separate payment records for each money event.
After recording or receiving payment, go to Finance -> Payment verification and confirm the payment verification behavior matches your process.
Payments overview
The mental model for deposits, service payments, verification, and reporting.
Understand deposits, service payments, refunds, purposes, and payment status.
Offline payments
How staff register cash, terminal, transfers, and other manual payments.
Record cash, terminal, bank transfer, and other payments received outside TatTool.
Revenue and reporting behavior
How payments become revenue numbers, and what service date vs payment date means.
Understand why revenue numbers appear, change, or stay out of reports.
Ready For Daily Use
Before the team starts, confirm:
- The first location and opening hours are correct
- Members have the right roles and invite emails
- Revenue targets and default locations are set where useful
- Payment methods and verification behavior match your process
- Required extensions are active and configured
- One booking and one payment workflow have been tested