Everything You Know About a Viewer, in One Place

Accounts, levels, devices, profiles, subscriptions and history all sit behind a single record. Look somebody up, see exactly what they see, and fix the problem before they have to ask twice.

Everything You Know About a Viewer, in One Place

A List of Accounts Is Easy. Answering a Question About One Is Not.

Almost any platform can show you a table of accounts. The table was never the hard part. The hard part turns up on a Tuesday afternoon, when somebody writes in to say they paid last month, the app disagrees, and nothing will play on the television in the spare room. Answering that means knowing which plan they are on, which devices they have signed in on, what they have actually watched and what the platform did the last time they opened it. When those four answers live in four different places, the reply takes a day. When they live behind one record, it takes a minute. Vodlix builds user management around the second shape.


Vodlix Signup & Sign in
Registration on your terms

Decide who can open an account and what they have to give you. Password length, username rules, an age floor, captcha, social sign in and email verification are all switches rather than code changes.

Vodlix CAS and User control manager
Viewers and staff kept apart

Registered viewers, administrators and staff each get their own view, and user levels decide what a person can reach. Whoever uploads your episodes never needs to see a billing screen.

Vodlix Device Management System
Devices, profiles and history

Every account carries its own devices, profiles, notifications, subscriptions, rentals and watch history. When a viewer tells you something is broken, you are looking at exactly what they are.

adm-users-list.png

Find Anyone in Seconds

The member list is your front door. Type a keyword to pull up one account, or move between the tabs to look at registered viewers, at administrators and staff, at your user levels, or at the lists you have grouped people into. Every row already shows the role, the account status, when the person was last active and when they joined, so most support questions get answered before you have opened anything at all. Bulk actions take care of the jobs that would otherwise be an afternoon of clicking, and import brings an existing audience across without anybody retyping it. The identities in the screenshot above are blurred for privacy. They are not blurred in the product.


adm-users-security.png

The Rules That Run Before Anyone Signs Up

Most of what goes wrong with accounts is settled long before a support ticket exists, in the settings that decide how people are allowed to join. Vodlix keeps all of it on one screen. Set a minimum password length and a username range. Open or close registration for the website and for the apps separately. Require email verification, write the wording of the verification page yourself, and choose where somebody lands once they have confirmed. Decide whether people sign in with an email and password, with a code sent to them, or with an account they already hold elsewhere. Keep a list of usernames nobody is allowed to claim. None of it needs a developer, and every part of it applies across the web, your mobile apps and your TV apps at once.


What You Can Actually Do to an Account

Opening one record gives you far more than a form. Change an email or reset a password. Deactivate an account, ban somebody who is abusing the service, or remove them altogether. Clear a stuck continue watching row that is spoiling somebody's home screen, or clear a cached response that is causing a fault nobody else can reproduce. Read their stats. When a problem only ever happens to one person, you can sign in as that person and watch it happen yourself, which turns a long thread of screenshots into about thirty seconds of work. From the same record you can move through their profiles, their devices, their notifications, their interests, their subscriptions, their rentals and purchases and their watch history without once losing your place.


It Does Not Stop at the Admin Area

Everything on these screens is also reachable from your own code through the REST API, so a customer relationship tool or a help desk you already run can read and write the same accounts rather than keeping a second copy of them. What people do once they are signed in feeds straight into reports and analytics and the sales dashboard. The profiles a household creates for itself are covered under profile selection, the lists viewers build for later under add to list, and the plans they are paying for under the subscriptions system.


Frequently Asked Questions

Have questions about taking advantage of this limited-time offer? Check out the FAQ for answers.

What is the difference between a user and a subscriber?
Every subscriber is a user, but not every user is a subscriber. A user is anybody who has an account on your platform, including people on a free tier, people whose trial has lapsed and your own staff. A subscriber is a user with an active paid plan attached. Manage Users covers the whole population, and the subscriber views narrow it to the people currently paying you.
Can I stop people from registering altogether?
Yes. Registration can be closed on the website and in the apps independently, so you can run an invitation only service, keep signup open on the web while an app build is still in review, or close it temporarily during a migration. Existing accounts carry on working while it is shut.
How do I give a colleague access without giving them everything?
User levels decide what each person can reach. Administrators and staff sit in their own view, separate from your viewers, and somebody whose job is uploading episodes can be kept well away from billing, settings and account records. Nobody needs a shared login, which also means you can see who did what.
Can I sign in as a viewer to reproduce a problem they are reporting?
You can. A single control on the account opens the platform as that person sees it, which is usually the quickest way to settle whether a fault is in the platform, in their plan or on their device. It saves the long exchange of screenshots that these conversations otherwise turn into.
What happens to somebody I ban?
A ban blocks the account from signing in while leaving the record and its history intact, which matters if the decision is later reversed or queried. Deactivating is the softer option and deleting is the permanent one, so you can match the response to what actually happened rather than having a single blunt control.
Can viewers sign in with a code instead of a password?
Yes. One time code login can be switched on alongside email and password, or made the only route in, and the code can be sent by email as well. In markets where phone numbers are the default identifier this usually converts better than asking people to invent and then remember another password.
Can I manage accounts from my own systems instead of the admin area?
You can. The same accounts are available through the Vodlix REST API, so an existing customer relationship tool, help desk or internal dashboard can create users, read their subscriptions and act on them without anybody opening the admin area. The admin area and the API work on one set of records, so the two never drift apart.
Can I bring an existing audience across from another platform?
Yes. The member list carries import and export controls, so accounts you already hold can be brought in rather than rebuilt one at a time. Anything the importer does not cover can be handled through the API, which is usually the better route when the migration also has to carry subscriptions or purchase history with it.