From ca8d0b3d2acc74f7061b922d05dab327ad81f7de Mon Sep 17 00:00:00 2001
From: John Kallies <3021949+JohnKallies@users.noreply.github.com>
Date: Tue, 14 Feb 2023 11:21:27 -0500
Subject: [PATCH] Correct out of date roles info in README

---
 README.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/README.md b/README.md
index 4095e7019..e3ee188f6 100644
--- a/README.md
+++ b/README.md
@@ -194,13 +194,13 @@ osmt_cli.sh -m
 * Keep in mind that removing Docker volumes will also remove this metadata. For more information, see the section for [Importing Data](api/README.md#importing-data) in the API README file.
 
 ### Role-based Access in OSMT
+* Role-based access is **enabled** by default for the Angular UI and Spring REST API.
+
 OSMT optionally supports role-based access, with these roles:
 - **Admin**: an OSMT user with an admin role can change RSDs and Collections in any way.
 - **Curator**: an OSMT user with a curator role can update but not create RSDs and collections. This role is for someone who would publish and unpublish RSDs and Collections
 - **Viewer**: an OSMT user with a viewer role is a logged-in user who can not make modifications to RSDs or Collections.
 
-Role-based access is disabled by default for the Angular UI and Spring REST API. Use these steps to enable roles.
-
 #### Configuration in OSMT Code
 By default, OSMT is configured with roles enabled. If you want to disable roles in OSMT, apply these changes: