First steps
This guide helps new users get started with the 3Q platform. It explains the basic steps required to set up an account, prepare projects, invite team members, upload on-demand content, start livestreaming, and embed media on external websites or applications.
The recommended onboarding workflow is:
Register and access your account
Set up projects
Create categories and types
Invite colleagues and assign permissions
Upload content and stream live
Embed and share your content
Registering an Account
To start using 3Q, you need access to a registered account.
Depending on your organization, the account may already be created by an administrator or provided during onboarding. After registration, users can log in to the platform and access the modules, projects, and features that are enabled for their account.
After signing in for the first time, check the following:
Your user profile is available
Your account is active (subscription)
The required modules are enabled
You have access to the projects you need
Your role includes the required permissions
Some features are controlled by account configuration and user rights. If a feature is not visible, it may need to be enabled or booked in Module Management or assigned through User Management.
Setting Up Projects
Projects are the main workspaces in 3Q. They define where content is uploaded, managed, streamed, recorded, or published.
Before uploading or streaming content, create or configure the projects you need for your workflow.
Common project types include:
On-Demand Projects Used for uploaded video and audio files that are processed, managed, and published as media assets.
Livestream Projects Used for live events, recurring streams, and live playback workflows.
When setting up a project, define the basic project settings, review access rights, and configure the metadata and publishing options required for your use case.
A common setup is to create separate projects or content pools for different departments, customers, brands, or workflows.
Example project structures:
Public Videos
Internal Training
Webinars
Townhalls
Product Videos
Event Livestreams
Podcast Episodes
Creating Categories and Types (optional)
Categories and types help structure metadata for on-demand content.
They are defined globally for the account and can then be used across projects and content pools. Per project or content pool, users can define whether all global categories and types should be available or whether only selected ones should be used.
This makes it easier to keep metadata consistent while still allowing project-specific workflows.
Categories
Categories are used to group content by topic, department, format, or editorial area.
Examples:
Tutorials
Product Videos
Town-Halls
Movies
Talkshows
Music Videos
Types
Types are used to define the content format or content purpose.
Examples:
Movie
Preview
Recording
Trailer
Webinar
Interview
Categories and types can later be assigned to on-demand assets and used for search, filtering, playlist automation, and frontend integrations.
Inviting Colleagues and Assigning Rights
After the account and projects are prepared, invite colleagues who should work with the platform.
User access is managed through User Management. Depending on their role, users can be allowed to upload content, edit metadata, manage players, create playlists, configure modules, or administer account settings.
When inviting colleagues, consider which responsibilities each user should have.
Typical roles include:
Account administrators
Project managers
Editors
Upload users
Livestream operators
Technical integration users
Read-only or review users
Assign permissions carefully so that each user has access to the features and projects they need, but not more than required.
If modules are enabled on the account level, users may still need explicit permissions before they can access or use them.
Uploading On-Demand Content
Once projects and permissions are ready, users can start uploading on-demand content.
On-demand content is managed inside an on-demand project or content pool. Uploaded files are processed by 3Q and then become available as media assets.
After uploading a file, users can manage the asset in the project’s asset management area.
Typical tasks include:
Reviewing the uploaded file
Editing title, description and other metadata
Assigning categories, types, and tags
Setting the release status (optiona)
Defining availability windows
Adding cover images
Managing audio tracks
Adding subtitles
Creating chapters
Preparing the asset for embedding or publishing
The asset detail view provides access to playback, metadata, cover images, audio tracks, subtitles, chapters, file attachments, and playout and sharing options.
Streaming Live
Livestream projects are used to receive and publish live signals.
To start livestreaming, create or open a livestream project and review the ingest settings. The ingest information is used by the encoder or production system to send the live signal to 3Q.
A typical livestream workflow includes:
Open the livestream project.
Copy the ingest endpoint and stream name.
Configure the encoder or production system.
Send a test signal.
Check the signal status in the livestream control center.
Start the live event.
Monitor playback and stream status.
Depending on the account configuration, additional livestream features may be available, such as Timeshift, Live Clipping, Livestream Distribution, or Livestream Recorder.
Live Clipping can be used when Timeshift is enabled and allows users to create clips from an active or previous livestream and export them to an on-demand project.
Livestream Recorder can be used to record livestream projects and store the recordings separately in a selected on-demand project or content pool.
Embedding and Sharing Content
After content has been uploaded, processed, or streamed, it can be embedded or shared.
Embedding is handled through the Playout and Sharing area. Depending on the content type and configuration, users can generate integration codes or links for websites, portals, applications, or external systems.
Common embed options include:
JavaScript embed code
iFrame embed code
Direct player URL
oEmbed link
Streaming URLs for custom players
For most website and application integrations, the 3Q Player Web SDK is recommended because it supports player configuration, subtitles, audio tracks, chapters, analytics, adaptive streaming, and other platform features.
When embedding content, select the appropriate playout configuration. The playout defines how the content is presented to viewers and which player settings are applied.
Playlists can also be embedded and used for structured playback experiences, such as video collections, video carousels, or vertical reel-style players.
Recommended First Setup Workflow
For a new account, the following setup order is recommended:
Register or activate the account.
Enable the required modules in Module Management.
Create the required projects and content pools.
Define global categories and types.
Configure project-specific metadata availability.
Invite colleagues through User Management.
Assign project and module permissions.
Upload first on-demand test content.
Create or configure a livestream project.
Test upload, processing, playback, and livestream ingest.
Configure players and playouts.
Embed the first video, livestream, or playlist.
This workflow ensures that the account structure, permissions, metadata, and publishing setup are ready before production content is added.
Typical First Use Cases
The first setup can support different workflows, for example:
Uploading and publishing on-demand videos
Creating a public video library
Managing internal training content
Streaming a live event
Recording livestreams for later on-demand use
Creating playlists and video carousels
Embedding videos on a website
Integrating 3Q with external systems through notifications or APIs
Notes
Available features may depend on account configuration, enabled modules, and user permissions.
If a module, project, or action is not visible, check whether the module is enabled and whether the user has the required rights.
For production workflows, it is recommended to test uploads, livestream ingest, player configuration, and embeds before publishing content publicly.
Last updated