| | 1 | == Application Design – Use Cases and Database Access Scenarios – SQL Views |
| | 2 | |
| | 3 | == Actors |
| | 4 | |
| | 5 | **Admin** |
| | 6 | |
| | 7 | * Can moderate content for appropriateness |
| | 8 | * Has a read-write permisions to the whole system |
| | 9 | * Can add or remove existing users |
| | 10 | * Can view platform analytics and user activity |
| | 11 | * Can manage and resolve reported content |
| | 12 | |
| | 13 | **Writer** |
| | 14 | |
| | 15 | * Has a read-write permissions to own content |
| | 16 | * Can add new stories and chapters, edit own stories and chapters |
| | 17 | * Has own reading list |
| | 18 | * Can collaborate with other writers through a permission-based system |
| | 19 | * Can view analytics on their stories |
| | 20 | * Can receive and accept/reject AI-generated writing suggestions |
| | 21 | * Can set stories as draft, published, or archived |
| | 22 | * Can manage mature content settings on their stories |
| | 23 | |
| | 24 | |
| | 25 | **Regular User** |
| | 26 | |
| | 27 | * Has a read-only permision of all stories and chapters |
| | 28 | * Can leave comments and likes to the stories |
| | 29 | * Can add stories to their reading list |
| | 30 | * Can report inappropriate stories or comments |
| | 31 | |
| | 32 | **Guest User (Unauthenticated User)** |
| | 33 | |
| | 34 | * Has a read-only permision of all public stories and chapters |
| | 35 | * Browse by categories or other filters |
| | 36 | * Cannot manage data in the system before registration or login |
| | 37 | |
| | 38 | == Scenarios |
| | 39 | |
| | 40 | == Most Important Use Cases |
