Opportunity is read-only

(5) Share

Report

Posted on by SHadleyP18

I have a user who was originally customer services, her role has changed and she now updates Opportunities. I have ensured her roles and teams are the same as another user in the Internal sales role but when she tries to amend an opportunity it says read-only although she seems to have the same permissions as the other person who can amend opportunities. I don't know where else to look, can anyone advise?

Categories:

Microsoft Dynamics CRM

I have the same question (0)

All responses (4)

Answers (2)

Suggested answer

Holly Huffman 6,538 Super User 2025 Season 2 on at

Like (1)

Report
Hi there! Good morning, evening, or afternoon - depending on where you are :) Hope you are well today!

This issue could stem from several factors. Here are some troubleshooting steps to help resolve it:

Security Role Permissions: Double-check the user's security role. Ensure that the role has the necessary permissions for the Opportunity entity, such as Read, Write, Append, and Append To. Permissions should be set at the appropriate level (e.g., User, Business Unit, or Organization).

Field-Level Security: Verify if any fields in the Opportunity entity are controlled by field-level security. If so, ensure the user has access to those fields.

Team Membership: Confirm that the user is part of the correct team and that the team has the necessary permissions for Opportunities.

Business Unit Hierarchy: If the user has moved to a different business unit, ensure that the permissions are correctly inherited or assigned for the new unit.

Record Ownership: Check if the Opportunity records are owned by another user or team. If so, ensure the user has the necessary access rights to edit records owned by others.

Form Customizations: Review the Opportunity form for any customizations or JavaScript that might be making the form read-only.

Editable Grids: If the user is working with editable grids, ensure that the grid settings allow editing and that field-level security is respected.

Audit Logs: Check the audit logs to see if there are any errors or warnings related to the user's actions on Opportunities.

If none of these steps resolve the issue, you might need to escalate the problem to your Dynamics 365 administrator, partner, or Microsoft.

Hope this helps some!

Was this reply helpful? Yes No
Verified answer

Daivat Vartak (v-9d... 7,835 Super User 2025 Season 2 on at

Like (2)

Report
Hello SHadleyP18,

This is a classic Dynamics 365 permission issue that can be tricky to troubleshoot! You've already done the right thing by comparing roles and teams, but there are some less obvious areas to investigate.

Here's a comprehensive breakdown of where to look and what to check:
1. Double-Check Role Assignments (Even if You Think You Did):

User Roles Directly:

Go to Settings > Security > Users.

Open the user's record.

Click Manage Roles.

Verify meticulously that all the roles assigned to the working user are also assigned to the problem user. Even a slight difference can cause issues.

Team Roles:

Similarly, check the roles assigned to the teams the user is a member of.

Go to Settings > Security > Teams.

Open each team the user is in.

Click Manage Roles.

Compare Team Membership: Make sure the problematic user is in the exact same teams as the working user.

2. Business Unit Permissions:

Business Unit Differences:

While less common, users in different Business Units can have different effective permissions, even with the same roles.

Compare Business Units: Confirm that both users are in the same Business Unit.

If they are in different business units, the security roles will behave differently.

3. Field-Level Security:

Field-Level Security Profiles:

Specific fields on the Opportunity entity might have Field-Level Security profiles applied.

If the problem user is missing access to a required field, the entire record might appear read-only.

Check Field Security:

Go to Settings > Security > Field Security Profiles.

Compare the profiles assigned to both users.

Check the permissions on the fields of the Opportunity entity.

4. Form Customizations:

Form Properties:

A form might have been customized to be read-only for specific users or roles.

Check Form Properties:

Go to Settings > Customizations > Customize the System.

Navigate to Entities > Opportunity > Forms.

Open the form the user is using.

Click Form Properties.

Look for any settings that might be making the form read-only.

JavaScript or Business Rules:

JavaScript or business rules on the form could be making it read-only based on specific conditions.

Review Customizations: Check for any JavaScript or business rules on the Opportunity form that might be affecting read-only status.

5. Opportunity Record Ownership:

Record Ownership:

If the problem user doesn't own the Opportunity record, and the organization's security model restricts access, the record might appear read-only.

Check Record Ownership:

Open an Opportunity record the user is trying to edit.

See who the owner of the record is.

Test with an opportunity that the user owns.

6. Browser Cache/Cookies:

Browser Issues:

Occasionally, browser cache or cookies can cause permission issues.

Clear Cache/Cookies: Ask the user to clear their browser cache and cookies.

Try Different Browser: Have the user try accessing Dynamics 365 from a different browser.

7. Dynamics 365 App Module:

App Module Differences:

If the users are using different D365 app modules, the app modules can have different security roles associated to them.

Ensure that the users are using the same App Module.

Troubleshooting Steps:

Start with Record Ownership: This is a common cause.

Meticulously Verify Roles and Teams: Don't assume they are the same; double-check everything.

Check Field-Level Security: Pay close attention to this.

Review Form Customizations: Look for any scripts or rules.

Clear Browser Cache: Rule out browser-related issues.

By systematically checking these areas, you should be able to pinpoint the cause of the read-only issue.

If my answer was helpful, please click Like, and if it solved your problem, please mark it as verified to help other community members find more.
If you have further questions, please feel free to contact me.

My response was crafted with AI assistance and tailored to provide detailed and actionable guidance for your Microsoft Dynamics 365 query.

Regards,
Daivat Vartak

Was this reply helpful? Yes No
Verified answer

Tom_Gioielli 2,792 Super User 2025 Season 2 on at

Like (3)

Report

This might be a silly question, but is the Opportunity closed? If an Opportunity has been closed as won or lost, it becomes read-only regardless of security roles assigned.

Otherwise, I recommend checking the security roles in more detail. Open the security roles that are assigned to your users, and search for the "Opportunity" table. Take note of what the "Edit" permission is set to:

None: The user cannot edit Opportunities at all

User: They user can only edit Opportunities where they are the owner

Business Unit: The user can edit Opportunities owned by themselves, or where the owner is in the same BU

Parent/Child Business Unit: They can edit Opportunities owned by themselves, or owned by a user in the same or a child BU

Organization: The user can edit any Opportunity across the system regardless or owner or BU

You can also open an Opportunity record, and at the top click on the "Check Access" button. Then enter in the users who you are checking. This should show what permissions they have been given, and which roles/team memberships are granting them. This is a great way to do a check outside of diving into the security roles and user settings themselves.

Was this reply helpful? Yes No
Vahid Ghafarpour 12,181 Super User 2025 Season 2 on at

Like (1)

Report

If any of the responses helped resolve your issue, please take a moment to mark the best answer. This helps others in the community quickly find solutions to similar problems.

To do this, simply click the "Does this answer your question?" button on the most helpful response and like the helpful posts. If your issue is still unresolved, feel free to provide more details so the community can assist further!

Thanks for being an active part of the Dynamics 365 Community!

Was this reply helpful? Yes No