Skip to main content
m3ter supports two types of user for your Organization:
  • Users. Represent the people you’ll grant access to your Organization.
  • Service Users. Intended to represent automated processes that you want to grant direct API access to your Organization. You’ll want to set up Service Users for integrations of your 3rd-party systems with the m3ter platform.
Using Permission Policies, you can then control what Users and Service Users can do when they have gained access. See Understanding, Creating, and Managing Permission Policies. From the Console Access page, you can:
  • View the details of Users, deactivate and reactivate them, and manage their access permissions.
  • Create User Groups and add Permission Policies to them. User Group are very useful for controlling access to your Organization when you want to set up a group of people and apply the same Permission Policies to them.
  • Invite Users to join your Organization and assign Permission Policies to control their access once they have joined. Invites can be made to either existing m3ter Users or people who are not yet registered with the platform.
  • Make a request to grant m3ter Support access to your Organization for a specified period.
This section explains how to manage the people and processes you grant access to your Organization in m3ter:
Important!Mixed Permission Policies - deny permissions take precedence: Care is needed if you set up a User’s access with more than one Permission Policy applied to the User. For example, you might assign the Administrator Permission Policy directly to a User at the level of their individual permissions. But if you then add them to a User Group to which a more restrictive Permission Policy has been applied - say one that denies all members of the group access to any Meters - then the more restrictive permissions imposed by the User Group Meter Access Denied policy takes precedence over the more permissive Administrator policy.Mixed Statement in a Permission Policy - denial takes precedence: If you create a Permissions Policy with multiple statements and two of more of the constituent statements conflict with respect to access to a resource for the given action, denial takes precedence - see Effects and Evaluation Logic for more details.