No guesswork. Just the next right step.

Step by step

1. 01

   Create the account

   Choose Start free or open the registration mode from Sign in. Enter your name, work email, and a unique password, then submit the form.

2. 02

   Verify the email address

   Open the verification message and follow its link. Return to Sign in afterward. A normal new registration creates an isolated workspace; an invitation joins the workspace named in the invite.

3. 03

   Review workspace basics

   Open Onboarding, choose Review workspace, and confirm the organization name, brand color, timezone, and currency. These defaults affect dates and financial displays across the product.

4. 04

   Choose a starting point

   Create a real show when you are ready to work, or add the clearly labeled demo show to explore safely. Demo data is available only to an admin in an otherwise empty workspace.

5. 05

   Bring in the team and services

   Use the launch checklist to invite teammates, connect services, add a partner, and model the first offer. You can complete these in any order.

6. 06

   Finish without losing the guides

   Mark onboarding complete when the core setup is ready. The checklist, migration form, and support tools remain available afterward.

Step by step

1. 01

   Open the event form

   Go to Events and choose New event. If you want to start directly with deal terms, open Offers & budgets and choose Create offer instead.

2. 02

   Enter the show identity

   Artist, venue, date, and capacity are the required anchors. Add city and state/region so calendars, reports, discovery, and partner views identify the market correctly.

3. 03

   Add the operating schedule

   Enter doors, show, curfew, and age restriction when known. Leave genuinely unknown details blank instead of adding placeholders that could be mistaken for confirmed times.

4. 04

   Choose the current status

   Use Hold for a tentative date, Offer while terms are out, Confirmed when approved, On sale for live inventory, and Settlement when final accounting begins.

5. 05

   Build the ticket scale and budget

   Open the event, then use Budget to add ticket tiers, inventory, comps, kills, prices, fees, taxes, royalties, and projected expenses. Marqueezy recalculates gross potential, net box office, break-even, and shares as assumptions change.

6. 06

   Set the artist deal

   Choose the deal type and basis, then enter the guarantee, percentages, backend threshold, alcohol terms, and offer notes that apply. Review the calculated artist payment and promoter position before saving.

7. 07

   Review and save

   Check the Overview and Offer tabs, save the working budget, and use Activity to confirm the record and its recovery points. Reopen the event whenever assumptions change rather than creating a duplicate.

Step by step

1. 01

   Add the partner organization

   Open Partner portals. Under Add partner, enter the organization name, choose agency, artist, venue, co-promoter, vendor, or other, and add the primary email.

2. 02

   Start a secure portal

   In Issue secure portal, select the partner and the exact event. A portal is event-specific; repeat this process when the same partner needs access to another show.

3. 03

   Reduce permissions to the minimum needed

   Offer & financials, day-of-show schedule, advancing, contracts, compliance, and shared comments begin selected. Uncheck every area the recipient should not see.

4. 04

   Create and copy the link

   Choose Create secure link and copy the displayed partner URL immediately. Send it directly to the intended recipient through a trusted channel.

5. 05

   Confirm access

   The recipient opens the link without creating a Marqueezy account. Use Issued portals to see whether the portal has been opened and which event it belongs to.

6. 06

   Remove access when necessary

   If the relationship ends or the link was shared incorrectly, have an admin remove the partner. Their secure portal links stop working, while retained event-history records remain.

Step by step

1. 01

   Create the draft

   Open Contracts & cash. Select the event and partner, give the agreement a specific title, and replace or extend the starter terms. The {{artist}}, {{venue}}, and {{date}} placeholders make the intended merge fields visible.

2. 02

   Review before sending

   Choose Create draft, then review the new item in Contract pipeline. Verify names, date, money, percentages, attachments, cancellation terms, and signature authority outside of assumptions.

3. 03

   Move the status forward

   Use the pipeline status to move the contract from Draft to Approval and then Sent. Do not mark it Signed merely because it was emailed.

4. 04

   Let the partner respond

   A partner with Contracts permission can open the secure portal, review the terms, and accept or decline. Keep the portal link private and verify that the correct partner is assigned.

5. 05

   Record compliance requirements

   Request items such as a W-9, W-8BEN, certificate of insurance, rider, invoice, or ACH documentation with an owner and due date. Update the checklist as items are received and approved.

6. 06

   Track the payment commitment

   Add the deposit, balance, vendor, co-promoter, refund, or other commitment with payee, amount, and due date. Update its status as the external payment process advances.

7. 07

   Automate the follow-up

   Optionally enable a reminder for upcoming payment due dates, signed contracts, received compliance, or on-sale status.

Step by step

1. 01

   Open connected reporting

   Go to Sales data. The provider strip shows supported reporting labels and highlights feeds already connected to the workspace.

2. 02

   Map the event

   Under Connect sales reporting, select the Marqueezy event, choose the provider, and add the provider event ID when you have it. The event ID helps keep similarly named shows separate.

3. 03

   Create the reporting feed

   Choose Create reporting feed. Copy the webhook URL and bearer token immediately; Marqueezy stores only the token hash after it is shown.

4. 04

   Configure the provider side

   Add the provided destination and token in the ticketing provider or approved middleware. Send sales reports for only the mapped event.

5. 05

   Use a manual snapshot when needed

   Select the event under Record sales snapshot and enter sold, capacity, gross, comps, and refunds. Use numbers from one timestamp so sell-through and gross are comparable.

6. 06

   Verify the latest report

   Check Sales pace by show for the provider, sold/capacity total, sell-through percentage, gross, and stored snapshot count. Correct the source mapping if the wrong event appears.

Step by step

1. 01

   Open Marqueezy while online

   Sign in and allow the workspace, operational data, and application shell to finish loading. The Mobile ops connection metric should read Online.

2. 02

   Name the device clearly

   Go to Mobile ops, enter a label such as Production office iPad or Door manager phone, and choose Trust this device.

3. 03

   Confirm it appears as trusted

   Find the device in Trusted devices. Admins can use its label, platform, status, and last-sync time to recognize stale or unexpected devices.

4. 04

   Refresh immediately before show day

   Reopen Marqueezy on the device while connected and visit the relevant event. This replaces an older cached snapshot with the latest available data.

5. 05

   Work within the offline boundary

   The application shell and latest snapshot remain available. Supported offer and operational updates can queue locally for replay after the connection returns.

6. 06

   Reconnect and verify

   When service returns, keep the app open long enough to replay queued changes. Confirm the updated record on a connected device before treating it as synchronized.

Step by step

1. 01

   Open the key creator

   Go to Enterprise and find Scoped API key. Use a descriptive name such as Reporting warehouse — production instead of a person’s name or a generic label.

2. 02

   Choose least privilege

   Select only the scope the integration needs. Create separate keys when two systems need different data or when read and write access should be isolated.

3. 03

   Create and store the token

   Choose Create API key, copy the full token from the shown-once result, and place it directly into the destination system’s secret manager.

4. 04

   Authenticate requests

   Send the token as a Bearer credential to the v1 API over HTTPS. Never place it in a query string, client-side bundle, screenshot, or shared document.

5. 05

   Verify with the smallest request

   Test the integration against the endpoint that matches the selected scope. A permissions error usually means the key needs a different scope—not that the existing key should be shared more widely.

6. 06

   Rotate deliberately

   Create a replacement key, update and test the integration, then revoke the old credential. Keep separate keys for development and production.

Step by step

1. 01

   Choose the protocol

   Open Enterprise → Identity & sessions and select none, SAML, or OIDC. Match the protocol actually configured in the identity provider.

2. 02

   Enter provider discovery details

   Add the HTTPS metadata or discovery URL and the verified company domain. These identify where Marqueezy should obtain trusted identity configuration.

3. 03

   Prepare provisioning

   Enable SCIM only when the provider-side application and deployment credentials are ready. Use the separate scim:read or scim:write scope for provisioning integrations.

4. 04

   Save before enforcing

   Save the identity controls with enforcement off. Complete provider activation and test sign-in with a noncritical account before locking the workspace to SSO.

5. 05

   Add narrow event overrides

   When a member should see only one show, use Event-level access to set edit, financial, and settlement permissions for that event.

6. 06

   Record governance evidence

   Use Compliance evidence to track a control key, human-readable control name, and status such as planned, implemented, verified, or exception.

7. 07

   Enforce only after validation

   Turn on Enforce SSO after the provider, domain, callback, certificates or client credentials, and recovery plan have all been tested in the deployment environment.

Step by step

1. 01

   Open the migration planner

   Go to Onboarding and find Plan a clean migration. Creating the request does not edit the source or import records automatically.

2. 02

   Name the current system

   Choose Spreadsheets, Prism.fm, venue-management software, ticketing exports, or another system so the intake can use the correct mapping approach.

3. 03

   Define the scope

   Select active shows/offers/budgets, contacts/relationships, documents/settlement history, or the complete workspace. Start with active operational data when historical files are inconsistent.

4. 04

   Set the target date

   Add the date the team expects to work primarily in Marqueezy. Leave enough time for mapping, a test import, reconciliation, and corrections.

5. 05

   Request the migration plan

   Submit the form. The tracked request asks the Marqueezy team for secure intake steps and the field-mapping template; follow that channel instead of emailing sensitive workbooks.

6. 06

   Prepare clean source exports

   Preserve stable IDs where available, keep dates and money values in consistent formats, separate people and organizations, and identify duplicate or cancelled records rather than silently deleting them.

7. 07

   Review the test import

   Check event counts, capacities, guarantees, ticket tiers, expense totals, documents, and settlement balances. Compare aggregate financial totals to the source before approving the final move.

8. 08

   Choose and document the cutover

   Agree when edits stop in the old system, complete the final delta import, and tell the team which system becomes authoritative. Keep the source archive for audit and rollback reference.