About Shell Statuses

Your shell can have one of four statuses.

Active: A live, in-progress shell.
On-Hold: The initial shell status. On-hold shells appear on the shells log. Shell administration functionality is available to shell administrators for setup and maintenance for users with permissions to perform that function. Users cannot create records in a shell that is On-Hold. If a user attempts to access a shell that is On-Hold, the system displays an alert message stating that the shell is On-Hold.
View-Only: View-Only shells can be viewed, printed, exported, and included in reports. You cannot modify any data in View-Only shells. This allows you to view past shells without allowing changes to these shells. If a shell in a shell hierarchy changes to View-Only, you can still navigate up and down the shell hierarchy, and can create sub-shells in the hierarchy under the View-Only shell.
Inactive: Used to suspend shell usage. Inactive shells are visible to Administrators, but not to end users. Only System and Shell Administrators (users with Modify Status rights) can reactivate the project.
Note: If automatic status update is enabled on a shell, the status of the shell can change from Active to an inactive status (On-Hold, View-Only, Inactive). The change of status is set up by the Administrator, and is based on defined triggering conditions. For example, if a shell is close to exceeding its funding, it might make sense to put it On-Hold while funding matters are discussed. Your shell administrator must manually change the status back to Active when you are ready to restart the project.

The Shell Administrator will receive email notification when the status of a shell changes. The change of shell status could occur due to a manual change, bulk update, through Web Services or a CSV file, or through automatic update.

See Also