1. Home
  2. Settings
  3. User access
  4. How to create user security profiles
  1. Home
  2. Person
  3. How to create user security profiles

How to create user security profiles

Security profiles determine what areas of Paragon a user can access, and what they can do in each module. This document will explain how to create and maintain these security profiles. Once your profiles are set up, you can assign them to users.

Step 1: Go to security profile setup

From any Paragon screen, hit the settings button at the top right corner of the screen.


On the settings screen, select the security option from the user access settings card to access the security module.


Step 2: Add a new security profile

The left hand side shows the list of security profiles that are already set up.

To add a new security profile, hit the create new security profile button at the top of the screen.


This is the screen that will appear.

Step 3: Add a profile name and owner

Enter a profile name and an owner.

Step 4: Set permissions

There are six types of permissions in Paragon.


Modules can only be set to visible or invisible. Module items can be set to invisible, readable, updateable, createable, and deleteable

  1. Visible – when you allow the user to view, create, update and delete what’s inside Paragon. This is the highest level of security a user can have.
  2. Invisible – when you make a section of Paragon invisible to the user (they will not see it when they log in).
  3. Readable – when you only allow the user to read what’s inside Paragon. They cannot delete, update, edit or create.
  4. Updateable – when you allow the user to update what’s already inside Paragon. They cannot create or delete anything, but can update what’s already there. This cannot be applied to reports or modules as they themselves cannot be updated.
  5. Createable – when you allow the user to create and update what’s inside Paragon. This cannot be applied to modules themselves or reports as they themselves cannot be created.
  6. Deleteable – when you allow the user to create, update and delete what’s inside Paragon. This is the highest level of security a user can have. This access cannot be applied to modules themselves or reports, as they themselves cannot be deleted.

Click on a module’s permission level to choose how users see and interact with each module.

Click on a module item’s permission level to choose how users see and interact with module items in Paragon.


When the System Administrator is checked, this means that the user will have full access to all modules and functions in Paragon.

Step 5: Save your changes

To save, hit the save button at the bottom right corner of the screen. To cancel, hit the red button at the top left corner of the screen.

You can now use the security profile to start creating user profiles. For more information on how to do this, click here. 


Updated on August 15, 2018

Was this article helpful?

Related Articles


  1. Gaby Berelovich

    Can we get a summary of what each permission means?
    What does Deletable mean? What does Creatable mean?
    Its not clear what these permissions will allow the user to do?

    1. Jon Ruby

      Good question. These are more generic terms related to database permissions referred to in the CRUD acronym; Create, Read, Update and Delete. Those four pretty much cover the functions that can be done in a data-based system. As relates to Paragon:
      -Create means you can create a new record like a customer or an invoice. Within a module it means those elements are part of what you have access to when you do create something new
      -Update means that a user can change something that someone else created, but not create something themselves
      -Read means that you can see a particular element on the screen, but cannot change it
      -Invisible means that you are actively choosing to make it so a users with this security clearance cannot see a particular element
      -Delete is well… you can’t really ever delete information easily in Paragon, but it means that you can remove it from the interface

  2. Gaby Berelovich

    Hi Jon, Thank you for the response. Quick followup question…
    From what I can tell, only one permission type is possible per module/module items, how would you set a user up to be able to Create and Delete? Does Create automatically allow a delete?

  3. Gaby Berelovich

    Hi Jon, I hope you don’t mind but as we get deeper in this user setup and security we have further questions. here they are;
    1) We would like to maintain our profile settings in excel as we work through testing and then we would compare one we start populating for the live environment. Is there a way to export the list of modules and Module Items, so as to not manually transfer them to excel?
    2) Why is the base permission for all modules and module items “deletable”? Seems like deletable is the most “risky” of the permissions.
    3) Does Paragon have default user profile setups? Example: Sales Agent one, or accounting manager, etc.
    4) What happens if at Module level we say invisible? Do we need to then change the permission to invisible for ALL the “module items” in that “Module”? or does the Invisible then push down from the higher “Module” level.

    That’s it for now. Thank you.

    1. Kayley

      Hi Gaby!
      You’ve brought up so many great questions, thank you. We’re currently reviewing the document above to include the answers you’re looking for. The changes will be available in the immediate future and once they are, we’ll let you know personally.

Add A Comment