Preface
RulePoint
RulePoint Concepts
- RulePoint Concepts Overview
- Understanding RulePoint Entities
Using RulePoint
RulePoint Objects
- RulePoint Objects Overview
- State of RulePoint Objects
Working with Topics
Working with Connections
Working with Sources
Working with Responders
Working with Responses
Working with Watchlists
Working with Analytics
- Analytics Overview
- Analytic Types
- Creating an Analytic
- Copying an Analytic
- Editing an Analytic
- Deleting an Analytic
- Viewing Related Objects
- Predefined Analytics
  - abs
  - average
  - ceil
  - charat
  - clean
  - compareto
  - concat
  - confidence
  - correlation
  - count
  - current
  - date
  - datedifference
  - endswith
  - even
  - floor
  - getcurrentdate
  - getdatefrommillis
  - getdateinmillis
  - geodistance
  - geoinbound
  - geoinsidearea
  - geointersect
  - geooutbound
  - geooutsidearea
  - geopassthru
  - indexof
  - integer
  - isblank
  - isholiday
  - isnum
  - istext
  - isweekday
  - isweekend
  - large
  - list2vars
  - lower
  - max
  - min
  - mod
  - mode
  - mround
  - odd
  - parse
  - past
  - percentile
  - power
  - proper
  - range
  - regex
  - replace
  - round
  - rounddown
  - roundup
  - sign
  - small
  - startswith
  - stdev
  - stringequals
  - stringindexof
  - stringlastindexof
  - stringlength
  - substring
  - sum
  - trim
  - truncate
  - upper
  - xpath
- Predefined Operators
  - contains
  - equalsSet
  - has
  - in
  - match
  - notMatch
  - search
  - unique
  - group by
  - distinct
  - unmatched
- Using the distinct, group by, and ummatched Filters
DRQL
Working with Rules
Working with Alerts
Setting Access Controls
Troubleshooting RulePoint Issues
Connecting to an Ultra Messaging Application
Creating an Ultra Messaging JMS Source

User Guide

6.2
- 6.1.2
- 6.1

Back Next

ACL Permission Rules

You can control RulePoint user or role access through ACL rules. The ACL rules require you to pass a set of requirements to gain access to a particular object.

In RulePoint, consider the following ACL rules:

If a user has ACL permissions for a project, that user inherits the ACL permissions for all the objects within that project, unless there is a more specific ACL permission entry at the object level that overrides it.

If a role has ACL permissions for a project, the user associated with that role inherits the ACL permissions for all the objects within that project, unless there is a more specific ACL permission entry at the object level that overrides it.

When a user creates an instance of an object, the ACL rule created for that object includes all the four permissions for that user, such as read, write, execute, and admin.

If a user creates an instance of the object, that user cannot modify the ACL settings in it.

Users with the super user privilege can access all objects irrespective of the ACL entry.

Rename Saved Search

Table of Contents

User Guide

User Guide

ACL Permission Rules

ACL Permission Rules