Product and implementation guide
Establish the event and responsibilities
Event Management is the ArcApps application for event planning and coordination. Confirm the planning, registration, schedule and follow-up capabilities included in your scope. Record the event's audience, location, date, time zone and responsible team. Identify who approves public information and who handles attendee questions.
Example: a workshop registration
A visitor submits a request for a workshop place. Define whether submission immediately confirms attendance or requires review. The acknowledgement should use the correct status and explain the next step. Test a repeated submission, a cancellation and a change of session if relevant. Capacity, ticketing and payment behavior must be confirmed rather than assumed.
Collect only necessary attendee details
Choose fields according to an administrative purpose. Avoid collecting identity documents or sensitive information merely because a template permits it. Provide a restricted route for accessibility arrangements and agree who can view those requests. Operational event messages should remain distinct from optional marketing subscriptions.
Rehearse the event-day handoff
Confirm how staff identify attendees and handle an unavailable connection or a registration they cannot locate. Protect any working exports or paper lists and reconcile changes after the event. Remove unnecessary temporary access and follow approved retention rules. The event registration guide provides a fuller preparation checklist, including confirmation wording and post-event ownership.
Access, setup and support
Start with a confirmed subscription and implementation scope, then use the sign-in address supplied by the team. The public website does not provision accounts. Your organization should identify an administrator, approve each user's role, and confirm which locations and records belong in the setup. Use unique accounts and follow the approved recovery process rather than sharing passwords. Confirm the available controls in your configured environment before entering live information.
Validate before going live
Prepare synthetic examples covering an ordinary workflow, a correction and a restricted action. Reconcile imported records against the approved source and agree who resolves differences. Ask each intended role to complete its tasks, including on the devices they will actually use. Record issues with the expected outcome and the observed result. Do not use real customer or employee records in a public demonstration.
Daily operation and changes
Keep operational policies and responsibilities alongside the configured workflow. When a task fails, note the time, action and visible error without sending credentials or sensitive records. Contact the support route agreed in your service terms. Changes to modules, integrations, exports, retention or commercial scope require confirmation; they are not implied by this guide. For onboarding and troubleshooting specific to your deployment, request a walkthrough using your approved scenarios.
Open the product guide · Product FAQ · Implementation support