Support

Help & Documentation

How every module works, step by step, in the cloud and on the desktop app. Search for a feature or a button, or browse by module below.

Getting started

Set up the workspace, learn the layout and understand who can do what.

Open the dashboard
5 topics in this module

What you can do here

Prezentra turns one workspace into a full service flow: build what goes on screen, plan the order of the service, then run every screen and a livestream from the same place.

  1. 1Produce is for running things: Dashboard, My Presentations, Livestream Studio, Live Studio and the Service Planner.
  2. 2Create is for building content: AI Creative Studio, Templates, Media Library, Worship & Songs and Bible & Scripture.
  3. 3Organize is for people and settings: Team, Analytics, Settings and this Help centre.
  4. 4Desktop app is for the production computer itself: physical monitors, offline decks and publishing directly from the machine.
  • Everything you make is shared with the rest of your workspace and isolated from every other organization.
  • The Dashboard is the fastest way back in: it shows the next services and whether anything is live right now.
  • The cloud and Prezentra Desktop use one account and one workspace — see Desktop & cloud for which does what.

Create your workspace

The first sign-in opens onboarding, where you name the organization and choose its type. That becomes the workspace name, brand and home for every deck, song and broadcast.

  1. 1Enter the organization name, then pick the type that fits (church, ministry, school, conference, nonprofit, corporate, individual or production team).
  2. 2Choose the primary and accent colours. They seed the workspace brand and can be changed later.
  3. 3Finish onboarding to open the Dashboard. Invite the rest of the team from Team once you are in.
  • Nothing in onboarding is permanent — Settings can rename, rebrand and reorganise the workspace at any time.
Open settings

Roles and who can control what

Each person in the workspace has a role. Everyone can open the library and look at content; the role decides who can run output and who can change the workspace itself.

  1. 1Owners and administrators manage settings, the team and the plan.
  2. 2Creative directors, production directors, presenters and volunteers can control live output from the control rooms.
  3. 3Presentation designers and worship leaders build decks, songs and media; read-only viewers can open content without controlling screens.
  • Change a role in Team at any time; it applies the next time that person loads a page.
Open Team

Signing in and resetting a password

Workspaces are invite-only. You sign in with the email address that was invited, using a password or Google.

  1. 1Use the sign-in page with your email and password, or continue with Google.
  2. 2Forgot the password? Request a reset from the sign-in page and follow the emailed link.
  3. 3If the workspace requires two-factor authentication, enter the code after your password or set up an authenticator when prompted.
  • No invitation yet? Ask a workspace administrator to invite the address you actually sign in with.
  • Invitations and reset links expire, so request a fresh one if the link no longer works.

Your first service in four moves

A reliable Sunday routine: build the deck, add the songs, write the rundown, then run the room. Each step uses a different module but they all stay linked.

  1. 1Build or generate the deck in My Presentations or AI Creative Studio.
  2. 2Add the songs to Worship & Songs and create lyric slides in one click.
  3. 3Write the service order in the Service Planner and link each presentation to its item.
  4. 4On the day, launch from the planner or open Live Studio, then control the room from the control room.
  • If you also stream, open Livestream Studio separately: it runs the broadcast program, not the auditorium slides.
Still stuck?

Ask your workspace administrator first — most blockers are access, plan limits or a device permission, and they can check all three. If the app itself behaves differently from what is written here, contact support and mention the module you were using.