Provisioning - Allow users to create spaces

As part of provisioning you can create space templates that Cisco Meeting Server web app users can use to create new spaces.

On the Provisioning page, Allow users to create spaces tab, you can create space templates, which will be available to all the users you have set up imports for on the Import users tab.

Limitations

You cannot use the templates to provision spaces for your users. The templates can only be used by the web app users to create their own spaces.
You cannot define which users get to use which space templates.

If you want to make different templates available to different users, then use the API to create and assign templates.
The user who creates a space is not assigned any of the roles that you define in Meeting Management. The space creator, who is also the space owner, will receive the default call leg profile for the space.
The user who creates a space will be a member of the space.
All members of a space will get the same call leg profile as the user who created it.

Note: Members can only be added using the Meeting App.
When you make changes to a template, not all changes are applied to existing spaces.

New Participant role settings and Space template settings are applied to existing spaces. Other template changes, such as adding or removing roles, do not affect existing spaces.

If you want to make changes to existing spaces, you can do this manually via the API.
The web app does not indicate to users if a template has been changed.

We recommend that you update the name or the description when you make significant changes to templates that are already in use.
Meeting Management provides a small subset of possible space settings.

If you want to configure additional settings to space templates you have created using Meeting Management, then you can use the API. See the "Create and apply coSpace templates" section of the the Meeting Server 2.9 Release Notes for instructions.
Templates that you have created or edited via the API will be visible in Meeting Management but you can only see the subset of the settings that can be edited in Meeting Management.

Some settings in Meeting Management are a combination of multiple API settings.

We have combined some settings to make it easier to configure templates.
The settings you configure using Meeting Management will replace any existing settings when you commit them.

This will only affect the specific settings that you configure. For instance, if you have defined a streaming URI for the space, this is not affected by settings you can configure from Meeting Management.

Sync error details are only stored in the Meeting Server system logs, and Meeting Management does not retrieve information about whether an LDAP sync has succeeded.

How to add a space template

To create a space template:

Go to the Servers page and click Set up provisioning.
On the Provisioning page, Allow users to create spaces tab, click Add space template.
Enter a space Template name.

This is the template name that users will see in the web app when they choose which type of space to create.

Note: If you use special characters in the template name, then they may appear differently in status messages, displaying escape characters instead. The name will still appear correctly in the web app.
Write a space Template description.

This is the template description that users will see in the web app when they choose which type of space to create.

Note: Meeting Management lets you enter more characters than you can commit to the Meeting Server. The limit for the Meeting Server is 200 bytes, which corresponds to up to 200 Roman characters with no accents, or around 50 Chinese characters.
Decide if different roles should be differentiated by their passcode, or if they should each have a unique URI and Meeting ID.

URI is called video address in the Meeting App and the web app.

Note: The Meeting Server recognizes roles by a participant's access method, which can be either the weblink or a unique combination of URI and passcode. Meeting Management will only add auto-generated passcodes if they are necessary to tell roles apart. web app users can add or change passcodes when they manage their spaces.

Note: If you are using Meeting Management version 2.9.0 and you want to change from using unique URIs to all participants having the same URI after you have saved the space template, then you must remove all roles and create new ones for the change to take effect.
Click Add role.
Enter a Role name.

This is the participant role name that web app users see when they choose which invitation details to send to someone.
Enter a Unique URI generator to define a rule for how the URI for the space is generated.

The URIs are created based on the space name, the URI generator, and the domain. For example, if you entered $.host, and a user creates a space called The A team on the domain example.com, then the URI would be the.a.team.host@example.com

Note: This field is disabled if you chose to use the same URI for all roles.
Click Next.
Check the Make this role an Activator check box if you want participants with this role to be Activators.

Activators can start meetings, and they can let other participants in from the lobby.

If you are creating a host and guest space, we recommend that hosts are Activators and guests are non-Activators. If you are creating a team space where you want all participants to have the same role, then you should make them Activators.
Configure permissions for the role.

For each of the listed settings, you can check the Override check box if you want to override the settings that are configured for the default space call leg profile. The default call leg profile is defined by a combination of factory settings and settings defined via the API.

Note: The web app has some limitations. For example, no participants can add others to a meeting or control streaming when they dial in using the web app no matter what permissions they have. See all limitations in the Cisco Meeting Server web app 2.9 Important information document.
Click Next.
Repeat adding more roles until you have added all the roles you want in this space template.

Note: All roles will be available in the web app. In the Meeting App, only one of these roles will be available in the invitation details, and no settings in Meeting Management can decide which role that will be.

To define which role should be used for the invitation in the Meeting App, you can use the Meeting Server API to set the scope field to public for the role that should be used for invitations sent from the Meeting App. See "Multiple coSpace Access Methods" in the Cisco Meeting Server API Reference Guide.
Click Next.
Define settings for the spaces that will be created from this template.

To use the system value for a setting, leave the Override check box unchecked.

To define a new setting, check the Override check box and choose the value that you want.

Note: If you want to define other settings than listed here, then you can adjust the templates via the Meeting Server API. See the Meeting Server 2.9 Release Notes for information.
Click Done.

Note: Your changes will not be applied before you have committed them. After you have committed the changes, template settings will take effect immediately. Changes to LDAP server details and user imports will take effect next time the Meeting Server is synchronized with the LDAP servers.

Note: All changes to provisioning settings that you have entered in Meeting Management will be lost if you restart Meeting Management before the changes have been committed.

Note: Meeting Management lets you enter more characters than you can commit to the Meeting Server. The Meeting Server limit is 200 bytes, which corresponds to up to 200 Roman characters with no accents, or around 50 Chinese characters.