Permissions

Submitted by Micky on Thu, 05/03/2007 - 17:15
tag(s) :

In an effort to give your users finer control over the system and their game servers Cortex sports a robust permissions system. Using this system you can give access to nearly any part of Cortex's functionality to any user or group. If a user doesn't have permissions to perform a function then the icon or form object to that function is hidden in cortex. For example, if you disable a user's filebrowser to an instance then they won't see it's icon on the Instances page. Permissions are assigned on the Groups page, but are viewable per user on the Users page, and give you access to a wide range of functions:

Engine Permissions

The top of the permissions page shows the user or group's permissions per game engine. Click the expand icon next to an engine to access permissions for that engine. Users have the ability to do the following:

 

  • Install: Install the engine.
  • Uninstall: Uninstall the engine.
  • Update: Update the engine:
  • Add instances of the engine for him or herself.
  • Add instances of the engine for anyone on the system.
  • Set a ceiling on the maximum amount of players allowed on their instances of this engine. This is limited to the maximum player value of the engine.

 

News Permissions

Give users access to the following news functions:

 

  • Add news articles.
  • Add news articles under the "custom" engine. The custom engine is defined in your skin as the engine used in news posts for news articles related to your company, clan, or group.
  • Edit any news article.
  • Edit only news articles that were created by that user.
  • Delete any news article.
  • Delete only news articles that were created by that user.

 

Clustering Permissions

The following clustering options are supported for users:

 

  • Add a server to to your cluster.
  • Remove a server from your cluster.

 

User Administration Permissions

Your user can have control over the other users on the system.

 

  • Add a user.
  • Remove a user.
  • Link users across your cluster.
  • Unlink users on a cluster.
  • Modify group permissions.
  • Change a user's skin only.
  • Modify others user's entire profiles.

 

Skin Permissions

If you choose your users or groups can work with the skins on the system as well:

 

  • Add a skin to the server.
  • Remove skins.
  • Edit a skin.
  • Set the system default skin.

 

System Settings Permissions

Nearly every system setting available in Cortex can be assigned to a user or group. Please give these permissions only to users that you trust.

Clustering Settings

  • Update clustering name and location.
  • Enable or disable the high-resolution timer.

Network Settings

  • Change Server Hostname
  • Add an IP address
  • Remove IP addresses
  • Change DNS resolvers.

Email Settings

  • Change General Settings.
  • Add an email template.
  • Edit email templates.
  • Remove email templates.
  • Change event recipients.
  • Change event templates.
  • Enable or disable event messages.
  • Change the email threshold. This affects how many messages per minute Cortex can send out.

System Restart

  • Reboot the system. Be careful when assigning access to this.

 

System Status Permissions

Limit your users access to view your server's system state. You can choose to show or not show them the following options:

 

  • CPU use
  • RAM use
  • Network use
  • Disk Use
  • Engine disk usage

 

Network Tools Permissions

By default all users can run all network diagnostics. If you choose you can limit what kind of tests they can run:

 

  • Only allow the user to run tests against their own IP address.
  • Allow ping testing
  • Allow tracerouting
  • Allow nslookup DNS resolution
  • Allow whois lookups.

 

Miscellaneous Permissions

There are various restrictions you can also place on your users. You can:

 

  • Allow or disallow FTP access.
  • Allow the user to add instances to the "admin" user's account. Usually only the admin account can do this.
  • Set a maximum number of instances the user can run at once. This is useful if you need to conserve system resources. Setting this to 0 disables the limit.
  • Allow a user to view news posts made by Insomnia365's staff.
  • Enable superadmin privileges. This gives your user the exact same privileges as the "admin" user. Be careful to assign this only to users that you trust.
  • Enable subadmin priveleges. Subadmins have all administrative privileges on the system with the exception of viewing and editing the "admin" user's instances.
  • Allow them to update their own profile.

 

Instance Permissions

Cortex lets you restrict access to nearly any instance function. Access is assigned per instance. Use the Select Instance drop down menu to select which instance you want to view or assign access to. The page will refresh showing the correct instance. Cortex lets you enable or limit access to the following instance functions. Actions marked with an asterisk (*) are usually admin only actions.

General Permissions

  • Activate the instance.*
  • Deactivate the instance.*
  • Delete the instance.*
  • Start the instance.
  • Stop the instance.
  • View the Event Log.
  • Check the instance's history graphs.
  • Use Cortex's remote console.
  • View instance status. If this is disabled then your user or group cannot view the ip, port, current map, hostname, and number of players conencted to your instance on the instances page.
  • Kick in-game users via the status page.
  • Ban in-game users via the status page.

Map Permissions

  • Apply a map rotation.
  • Modify the current rotation's map order.
  • Add a map to the rotation
  • Remove a map from the rotation.
  • Upload a map to the server.
  • Remove custom maps from the server.
  • Create new map rotations.
  • Remove map rotations.
  • Change map rotations.

Configuration Permissions

  • View the RCON password.
  • Edit the RCON password.
  • Edit the instances max player value.*
  • View the instance's command line.*
  • Edit the instance's command line.*
  • View instance comments.*
  • Edit the instance's comment.*
  • Transfer the instance to another server on your cluster.*
  • Change the instance's IP address.*
  • Change the instance's port.*
  • Change the instance's processor affinity.*
  • Create a new configuration.
  • Change active configurations.
  • Delete configurations.
  • Export the current configuration to the browser.
  • Save the current configuration to a local file.
  • View the basic config form.
  • Edit the basic config form.
  • View the advanced config form.
  • Edit the advanced config form.
  • View admin level cvars in the config form.*
  • Edit admin level cvars in the config form.*
  • Import configs.

File Browser Permissions

  • Enable or disable the filebrowser.* If you disable the filebrowser then your user won't see this instance on the FTP server.
  • Create .zip archives.
  • Create directories.
  • Download files.
  • Extract .zip files.
  • Create text files.
  • Copy files.
  • Delete files.
  • Edit text files within Cortex.
  • Move files.
  • Rename files.
  • View files within Cortex.
  • Upload files.

Plugin Permissions

  • Activate plugins.
  • Deactivate plugins.
  • Install plugins.*
  • Remove plugins.*
‹ Groups Instances ›