Permission Groups & Sets

Learn about Permission Sets & Groups in Maica

Useful Definitions

How is Permission Managed in Maica?

In Maica, Permission is managed by leveraging Permission Sets and Permission Set Groups, using a layered approach to enable flexibility.

Every custom object in Maica—such as Appointments, Invoices, and Notes—as well as any core Salesforce object that Maica interacts with, has corresponding Permission Sets. These will fall into one of two categories:

  1. Object-based, which control access to individual objects (Create, Read, Edit, Delete)

  2. Functional, which control access to Maica functionality like claiming or integration tools.

Then, to simplify assignment to Users, these Permission Sets are categorised into Permission Set Groups, allowing you to quickly apply the right combination of access for specific roles or responsibilities.

If you need guidance assigning Permission Sets or Permission Set Groups to users in Salesforce, click here.

Permission Breakdown

So, let's break it down further.

Permission Set Groups

As mentioned, Permission Set Groups are used to bundle multiple related Permission Sets together. These groups represent a functional area or role—for example, the Manage Invoices & Object Permissions set groups together Billing related Permission Sets.

When you assign any Permission Set Group to a user, they inherit all the individual Permission Sets contained within that group. Using our example of the Manage Invoices & Object Permissions group, any User assigned this Group would gain permission sets for Invoices, Payments, Logs, Support Items, and more.

Permission Sets

As also mentioned, each Permission Set in Maica falls into one of two categories:

1. Object-Based Permission Sets

These sets grant access to core Data Objects in Maica and are broken down further based on the CRUD model:

  • Create

  • Read Only

  • Edit

  • Delete

Each object in Maica—such as Invoices, Appointments, or Accommodation—has its own four distinct Permission Sets, one for each of the access types listed above. For example, the object “Accommodation” has four separate permission sets:

  • Maica – Accommodation – Create Access

  • Maica – Accommodation – Edit Access

  • Maica – Accommodation – Delete Access

  • Maica – Accommodation – Read Only Access

Object-based sets ensure granular control over what users can do with individual data types in Maica—whether that’s just viewing a record or creating and editing new ones.

For a detailed breakdown of the Object and Field-level Permissions included in each access type, see the section below.

2. Functional Permission Sets

Functional sets control access to a specific feature or process within Maica. These aren’t tied to single objects, but rather to functional workflows. For example: Submitting NDIS Claims.

These sets typically include logic or automation in the background and often require users to have appropriate object-level permissions in place as well.

Object-Based Permission Structure in Maica

As mentioned above, each object in Maica has its access broken down into four Permission Set types: Create Access, Edit Access, Delete Access, and Read Only Access.

It’s important to clarify the distinction between:

  • The object itself (e.g. Accommodation, Invoice), and

  • The Object Permissions applied within a Permission Set for that object (e.g. Read, Edit, View All Fields).

Each Permission Set corresponds to one access type for one object (e.g. Maica - Accommodation – Create Access) and includes Salesforce-defined Object Permissions and Field Permissions to control what users can do.

For every Object Permission Set, you’ll find two key areas:

  • Object Permissions: Define what a user can do with the object as a whole (e.g. create or delete records, view all fields).

  • Field Permissions: Define which individual fields a user can read or modify on that object.

In Salesforce, Field Permissions are often referred to as FLS

The table below outlines what is included in each type of Permission Set:

Permission Type
Object Permissions
Field Permissions

Create Access

- Read - Create - View All Fields

- Read Access (on all required fields) - Edit Access

Edit Access

- Read - Edit - View All Fields

- Read Access - Edit Access (on editable fields)

Delete Access

- Read - Edit - Delete

- Read Access - Edit Access (on editable fields)

Read Only Access

- Read - View All Fields

- Read Access only

Let’s take a closer look at how this structure works using the Maica - Accommodation – Create Access Permission Set as an example, as shown below.

Object Permissions

As this is a Create Access Permission Set, the following object-level permissions are enabled:

  • Read

  • Create

  • View All Fields

Field Permissions

And, underneath the object-level access, field-level access is also defined. For a Create Access Permission Set like the one shown, the user has:

  • Read Access

  • Edit Access

To learn more about the breakdown of Permission Set Groups in Maica and see descriptions of what each group provides access to, click here.

Last updated

Was this helpful?