Troubleshooting: cda.org User roles and permissions

General information:

If a user reports they are unable to view content on either http://cda.org or http://tdicinsurance.com that requires a login to view, please have them do the following:

  1. Confirm they are actually logged in (their name should be at the top right of the screen)

  2. If logged in and not able to access something, have them log out and return to the login page, then try to recreate the error. Restarting their browser or even clearing their cache can sometimes solve the issue.

  3. If they still cannot access the content, you will need the following information to troubleshoot:

    1. Username they are logging in with

    2. Page URL

    3. Name or description of the content that they are not seeing

    4. Ideally, a screenshot of what they are seeing, or have them read any error message they are seeing.

  4. Please also confirm that the information they are looking for is visible to you as an admin.


Viewing User Roles and Information

  1. If you have an account tied to ebusiness, log in at the top right of the http://cda.org site. If you only have a DNN admin login, you will need to use the login page at cda.org/admin-login

  2. To view user information, go to the “users” page from the persona bar

3. Use the search bar to locate the user. Some users may have multiple logins, which is why you need their email address.

4. Click on the shield icon to view the user’s permissions. Typically you are looking to make sure the user has the permission “cdamember”

5. If the user was unable to login at all, you can also verify that they are not locked out through the settings (gear icon). This view also shows information such as when they last successfully logged in.

 

If the user has the correct role assigned, is not locked out, and is logged in with the correct username, then the issue may be in Aptify. The member services team will need to verify that in the membership details section of the user’s account, they have the “http://cda.org ” access checkbox selected.

In select cases, such as when the issue is with a content editor not being able to edit something, the issue may be at the page or module level.

Page and Module Permissions

 

  1. Check the permissions of a page at the bottom left using the “settings” icon.

2. If the page has a box checked in the view column for “all users”, then any user may visit this page, but there may be special permissions on a page section.

3. Navigate to the top of a section, or module, and select “settings.”

4. In the section below, the box for all users is NOT selected. The module will only be visible to users with the permissions “CDAMember” or “Component Executive Directors”, as well as specific content editor roles.

Verifying Roles

If you need to see all users in a certain role, follow these steps.

  1. In the same section as where users are managed, select “Roles”

2. Select “All Groups”

3. Search for the role or use the load more button to browse. Click the person icon to see all users in that role.

 

 

 

 

 

 

 

Known issue: If an end-user clicks on a link that requires a login, they are currently going to be taken to an error page after logging in. The system is supposed to redirect them to the file or page they needed to access, but currently does not.

 

Content Editor Roles

If a user reports they are not able to edit content, upload files, or view form results, there are separate roles for these items, set up the same as outlined above.

There are multiple content editor roles, including a global “content editor” role that allows editing most content pages, as well as specific roles such as “CDA Presents Content Editor” and CDA Foundation Content Editor.” In order to edit content, the user and the page must both have this role, and the checkbox under “edit” must be selected. For example:

 

 

Related pages