beA is part of firm operations
The German Federal Bar provides beA as a central electronic legal communication channel. Its technical operation therefore becomes part of deadline-driven workflows.
One working PC is not an operating model. Access, roles, cards, client components and support paths need to be accountable.
Manage roles and access clearly
Personal accounts and assigned permissions make actions traceable. Shared credentials and permanently open administrator rights increase risk and complicate support.
Joining, leaving and substitution should be documented as repeatable processes.
Keep workstations and updates predictable
Browsers, beA components, signature tools and firm software follow different update cycles. Changes should be tested away from critical deadlines.
At least one prepared alternative workstation can improve resilience during a local failure.
Network, internet and recovery
Stable internet, protected DNS and firewall configuration, and documented networks are part of the service chain. Alternative connectivity should be assessed where outage impact is high.
The recovery plan records internal contacts, external support paths and the order in which systems return.
Sources and scope
Official information is provided by BRAK at https://www.brak.de/anwaltschaft/bea-erv and the beA support portal at https://portal.beasupport.de/.
JITIS designs technical infrastructure and documents operations. Legal advice and professional responsibility for deadlines are outside the service scope.