Summary: Specification and functional overview for extending user profile picture editing capabilities in the Church App to Breeze.
Feature Specifications & Permissions Matrix
The Edit button and editing capabilities on the main Profile screen dynamically follow the user's role and permission settings in the underlying platform.
| Platform | User Role | Profile Edit Permissions | Profile Picture Deletion | Profile Data Editing |
| Breeze | Admin | Full profile edit permissions | Not Supported (Breeze API limitation) | Follows per-field permissions |
| Breeze | Member | No profile edit permissions | Not Supported | None |
Key Functional Workflows
Accessing the Edit Screen:
When a user views their main Profile screen, the Church App checks their permissions against the backing platform.
If the user lacks profile edit rights (e.g., a standard Breeze Member), the Edit option is hidden.
Updating or Deleting Profile Pictures:
Breeze Users: Options are provided to upload or replace a profile photo. The option to delete an existing photo is omitted because Breeze does not support picture deletion.
Editing Profile Fields:
Breeze Users: Form fields enforce granular per-field permissions set in Breeze.
Troubleshooting & FAQs
Why is there no option to delete a profile picture for a Breeze user?
The Breeze backend platform does not support profile picture deletion via API. Users can replace their picture with a new image, but cannot remove it entirely.
What if a Breeze user has permission to edit some fields but not others?
The Church App enforces field-level permissions returned by Breeze. Fields that the user is not permitted to change will remain read-only.
Does the mobile app need to handle multi-step uploads for Breeze?
No. All platform-specific API steps are abstracted and processed on the Apps Backend, keeping the client-side mobile code clean and unified.