perobject

Perobject, often written as per-object or per object, is a term used in software engineering to describe mechanisms, policies, or data that are attached to or evaluated for individual objects rather than at the class or global level. The concept appears across object-oriented design, security, data modeling, and configuration, and it enables fine-grained control and customization at the cost of added complexity.

In access control, per-object permissions mean that authorization is determined for each item (such as a specific record, file, or resource) rather than by role alone. In data modeling and serialization, per-object metadata or behavior means that each object carries its own settings or state. In configuration management, per-object configuration allows different settings for instances of the same type.

Advantages of perobject approaches include greater flexibility, precision, and the ability to tailor behavior to individual objects. Disadvantages can include increased storage or processing overhead, more complex logic to maintain consistency, and greater burden on development and maintenance.

Note that perobject as a single word is not a widely standardized term. Most references use hyphenated or spaced forms (per-object, per object). In practice, the concept is descriptive rather than a formal API name, and it is implemented differently across frameworks and domains.

See also: object-level permissions, per-object encryption, per-object configuration, object-oriented design, fine-grained access control.