What's the Difference Between Private and Public Workspaces and Events? – Social27 Events

In the Social27 Events Platform, you can control which users have access to your workspaces and events, ensuring that the right users register for the right events.

Public, Private, and Hidden Events

When you create an event, you can set the event type:

Hidden: Only available to people with the link
Public: Available to everyone and listed on Social27's events
Private: Only available to people with the link and event password

If an event is public, it will be listed in the Public Events tab users see when they log in to the Social27 platform. If the event is private, it will instead appear in the Your Events tab.

Public and Private Workspaces

If you would like to further refine access to your events, you can navigate to the Workspace Access tab and edit your workspace. If you set your workspace to public, anyone who is given the workspace URL can view the workspace page and can register for any public events in that workspace. (Private events will require the user to log in to access.)

If you set your workspace to private, users must log in to view the workspace page and events contained din the workspace.

For more information about workspace access, check out this article.

Mixing Public and Private Events and Workspaces

Check out the table below to understand the various private/public workspace and event combinations you can create:

Workspace	Event	Access
Public	Public	Users can access the workspace page and event registration form.
Public	Private	Users must log in to the Social27 platform view the workspace page and will see only the events to which they have been given access. (For more information, review this article.)
Public	Hidden	Users can only access the event by logging in directly from the event URL.
Private	Private	Users must have credentials to access the workspace page and will see only the events to which they have been given access. (For more information, review this article.)
Private	Hidden	Users can only access the event by logging in directly from the event URL.

Further Reading :