Skip to Content

Specifying access restrictions for your workspace

TwentyThree makes it easy to create your own video universe and share it with the world. However, you may be in a situation where you wish to limit access to your video content. This could be the case if you:

  • Have videos with sensitive information that only employees in your organization should be able to see.
  • Wish to have visitors pay to see your content.
  • Have content that only visitors from specific geographical areas should be allowed to watch.

To accommodate the many different needs of access-restriction, your TwentyThree website can be set up with one of six ways of controlling your visitors' access. Please note that these access restrictions only apply to pages and videos directly on your video hub. You always have the option of embedding your videos elsewhere, regardless of your choice of access-restriction.

Public website

With this setting, your video hub will be publicly available on the internet, and visitors will be able to watch all videos you have published and placed in a category.

Restricted site

Only users with a user account (either regular or administrative) to the backend of your video hub will be able to see the site and the videos on it. Visitors will be asked to log in when they try to enter the site.

Shared password

This setting allows you to specify a single password or passphrase that grants access to the video hub. You can distribute this single password to all users (eg. event attendees) that you have and they will all use the same password to browse your video website and the videos that you have published.


By setting up a firewall you can specify which IP addresses or IP ranges that are allowed to browse your video hub and watch your videos. If a visitor accesses your site from an IP that is outside the ranges you have specified, he or she will be presented with a login form.

Single sign-on 

If you want to have 100% control of who has access to your video hub, you can maintain your own user database (or make use of an existing one) and grant users authorized access based on this. This solution requires integration with TwentyThree's API for authorizing users. Use this option if you wish to provide single sign-on functionality for users of your intranet.