Page tree
Skip to end of metadata
Go to start of metadata

Objects in 25Live have two levels of security which determine how users can interact with them:

  • Object security, also known as "editing permissions", which determines who is allowed to see an object's details and make changes
  • Assignment policy, which determines who makes requests and who approves them (available only for locations and resources)

Learn how to configure these settings at Editing Object Security and Assignment Policy.

Object Security

Object security sets the basic level of interaction a user is allowed to have with a location, organization, report, or resource in 25Live.

There are four levels of permissions for a given object which grant the following actions:

  • Edit, Delete, Copy
  • Edit
  • View Only
  • Not Visible

For the vast majority of users, View Only rights are the most appropriate setting. This includes reports, as users do not need permission to edit a report in order to run it.

Use lower permissions (Not Visible) when you want to hide objects from a user, and use higher ones (Edit or better) when you want a user to have administrative powers over an object, including changing its name and other vital statistics.

Assignment Policy

Assignment policy dictates how a user interacts with a location or resource during the scheduling process. It determines whether a user is able to request or assign an object, whether they can unassign it from existing events, and whether they can approve requests from others.

Organizations don't have assignment policy!

Please note that assignment policy affects locations and resources only. Anyone who has permission to view an organization is able to attach it to events without requiring approval. If you wish to set up an alert that an organization has been used, consider using notification policy

There are five levels of assignment policy with the following permissions:

  • Assign, Unassign, Approve
  • Assign, Unassign
  • Request, Unassign
  • Request
  • Not Requestable

These levels have different combinations of the same basic permissions. 

  • Assign permissions allow a user to directly assign a location or resource to an event. As soon as the assignment is complete, the location is unavailable for others to assign.
  • Users with Request permissions can choose to add a location or resource, but it is not fully assigned until it is approved. Others may still assign or request it for events at the same time.
  • Unassign permissions allow a user to remove a location or resource from an event, making it available again. Users without this ability trigger a request for unassignment which is not carried out until approved.
  • Requests for assignment or unassignment are sent to users with Approve permissions as workflow tasks. Once approved, the (un)assignment is carried out as normal.
  • A location or resource which is Not Requestable is still visible in searches and calendars, but cannot be requested for events.

A security group's default assignment policy on locations can be temporarily overridden by assignment windows when creating or editing events that take place in the near future.

Assignment Windows and "Not Requestable"

If a location's default assignment policy is Not Requestable, then assignment windows do not have an effect.



Copyright © 2021 CollegeNET, Inc.  Note: This information is for CollegeNET Series25 customer use only.
Series25 Customer Resources • Terms of Use •  Privacy Policy • Learn About Series25 • Contact CollegeNET