ActionPermissionType Enumeration

Assembly: CodeEffects.Rule.Common.dll
Namespace: CodeEffects.Rule.Common.Models

Summary

Identifies something a user can do in the Rule Repository, and therefore something a host can grant or withhold. There is one member per permission.

Syntax

public enum ActionPermissionType
{
	Undefined = 0,
	SourceUpdateDetails = 10,
	SourceDelete = 11,
	SourceVersionUpdateDetails = 20,
	SourceVersionGoLive = 21,
	SourceVersionTakeOffline = 22,
	SourceVersionDelete = 23,
	RuleCreate = 30,
	RuleUpdateDetails = 31,
	RuleDelete = 32,
	RuleVersionCreate = 40,
	RuleVersionUpdateDetails = 41,
	RuleVersionGoLive = 42,
	RuleVersionTakeOffline = 43,
	RuleVersionRequestApproval = 44,
	RuleVersionApproveAndDecline = 45,
	RuleVersionDelete = 46,
	DraftView = 50,
	DraftCreate = 51,
	DraftUpdate = 52,
	DraftConvert = 53,
	DraftDelete = 54,
	TestView = 60,
	TestRun = 61,
	TestCreate = 62,
	TestUpdate = 63,
	TestDelete = 64,
	TestRunBatch = 65,
	TestRunProductionCalls = 66,
	ValueTemplateCreate = 70,
	ValueTemplateUpdate = 71,
	ValueTemplateDelete = 72,
	EvaluationView = 80,
	EvaluationSaveAsTest = 81,
	ActivityView = 90,
	NoteView = 100,
	NoteCreate = 101,
	NoteDelete = 102,
	AiAssistantUse = 110,
	AiRuleEditorUse = 111,
	AiConversationViewAll = 112
}

Members

Remarks

The set is flat: a list of these values, read according to an ActionPermissionMode, handed to the Rule Repository's configuration or answered by its permission check on every request. How the members depend on each other is the Repository's own map: withholding a permission withholds every permission that requires it.

The values are a contract. A host stores them in its own roles table or configuration, to decide what the signed-in user may do. An existing member is never renumbered or reused for something else, and new members are appended. The numbers are grouped by object in tens, and the gaps are intentional.

The four core objects (source objects, source versions, rules, and rule versions) have no view permission: every Rule Repository user sees their grids and opens their dialogs. Drafts, tests, evaluations, user activity, and notes have one, and without it everything about them is hidden and withheld.

Creating a source object or a source version is deliberately absent: both are the host's own doing, never a user's. Some actions are a person's only, whatever the set says: making a version live or taking it offline, approving, declining, and deleting.

The enumeration lives in the Common assembly, not in the Repository, so that code which cannot reference the Repository can carry and check a set of permissions.

Example

using CodeEffects.Rule.Common.Models;

// A reviewer who may read tests and run them, but nothing else
var mode = ActionPermissionMode.AllowOnly;
var list = new[]
{
	ActionPermissionType.TestView,
	ActionPermissionType.TestRun
};