A clear job
EventManager should own the work in its name and avoid quietly becoming the database for every neighboring tool.
PLAN THE TRIP
Plan the event once, then connect the details everywhere else.
Coordinate dates, registration details, transportation, documents, and event references that other tools can read without duplicating ownership.
Use a screenshot that shows the tool doing its most recognizable job.
EventManager should own the work in its name and avoid quietly becoming the database for every neighboring tool.
When another tool needs trusted information, it can read it without creating a second conflicting copy.
Automation should suggest, prepare, and reduce repetition while leaving consequential ministry decisions visible to people.
PLACEHOLDER FOR THE SECOND STORY
The second screenshot should not repeat the first at a slightly different zoom. Use it for a mobile workflow, display mode, focused editor, report, or other view that explains why this tool belongs in the suite.
Use a tighter detail, mobile view, or display interface.
EDIT IN ADMIN → SCREENSHOTS