Before setting up Team Members users in Business Central 25, ensure all prerequisites are met to guarantee a smooth implementation.
Administrative Requirements
System Access
-
SUPER permissions in Business Central 25
-
Administrator access to Microsoft 365/Azure AD tenant
-
Security Administrator role for user management
-
License Administrator role for license assignment
License Availability
-
Sufficient Team Member licenses in your subscription
-
Understanding of license limitations and capabilities
-
License compliance documentation and tracking
-
Cost center approval for license assignments
Technical Prerequisites
Azure AD/Microsoft 365 Setup
-
Users must exist in Azure Active Directory
-
Valid email addresses for all users
-
Proper domain configuration for single sign-on
-
Multi-factor authentication configured (recommended)
Business Central Environment
-
Business Central 25 (Online or On-Premises)
-
Latest cumulative updates installed
-
Sveitarstjóri Wise extensions installed and configured
-
Municipal dimension setup completed
Security Planning
Permission Strategy
Plan which permission sets to assign:
Standard Permission Sets:
-
TEAM MEMBER - Core Team Member functionality
-
D365 TEAM MEMBER - Standard read access
-
D365 READ - Basic read permissions
Optional Permission Sets:
-
WORKFLOW APPROVAL - For users who need to approve
-
TIMESHEET - For time tracking functionality
-
D365 JOURNALS, POST - If limited posting is needed
Dimensional Security
-
Municipal assignments defined for each user
-
Global Dimension 1 filters configured
-
Global Dimension 2 filters set up if needed
-
Field class access planned for each user role
User Information Requirements
Basic User Data
For each Team Member user, collect:
Required Information:
-
Full name (Display Name)
-
Email address (Authentication Email)
-
Department/Municipality assignment
-
Manager/Supervisor information
-
Start date and access duration
Optional Information:
-
Phone number
-
Office location
-
Cost center
-
Employee ID
-
Language preference
Role Assignments
Define for each user:
Functional Role:
-
Department head
-
Financial analyst
-
Project manager
-
External consultant
-
Auditor
Access Scope:
-
Municipal boundaries
-
Departmental limits
-
Time-based restrictions
-
Specific field class access
System Configuration Prerequisites
Municipal Setup
Ensure the following are configured:
Municipality Dimension Management:
-
Municipality codes defined
-
Dimension relationships established
-
Municipal boundaries set
-
Access hierarchies configured
Field Class Configuration:
-
Income/Balance classifications set up
-
Field class codes defined
-
VAT setup completed
-
Reporting structures in place
Account Structure
Verify account setup:
Chart of Accounts:
-
Account numbers defined
-
Income/Balance categorization complete
-
Totaling accounts configured
-
Budgets established
Dimension Setup:
-
Global dimensions configured
-
Department dimensions defined
-
Project dimensions established
-
Shortcut dimensions assigned
Documentation Preparation
User Documentation
Prepare user guides for:
Getting Started:
-
Login procedures
-
Navigation basics
-
Role center orientation
-
Basic functions
Functional Guides:
-
Account Budget Overview usage
-
Report generation
-
Excel export procedures
-
Workflow participation
Administrative Documentation
Create admin guides for:
User Management:
-
Adding new users
-
Modifying permissions
-
Troubleshooting access
-
License monitoring
Security Management:
-
Permission set assignments
-
Dimension security setup
-
Access troubleshooting
-
Compliance reporting
Training Preparation
User Training Plan
Develop training for:
Basic Navigation:
-
Role center usage
-
Search functionality
-
Report access
-
Help system usage
Functional Training:
-
Account analysis
-
Budget variance review
-
Dimensional filtering
-
Export capabilities
Administrator Training
Ensure admins understand:
User Management:
-
Team Member limitations
-
Permission assignments
-
License compliance
-
Security principles
Troubleshooting:
-
Common access issues
-
Permission problems
-
License violations
-
Performance optimization
Environment Considerations
Performance Planning
-
User load assessment - How many concurrent users?
-
Data volume analysis - How much data will be accessed?
-
Network requirements - Bandwidth and latency considerations
-
Peak usage planning - When will most users be active?
Backup and Recovery
-
Current backup strategy validated
-
Recovery procedures tested
-
User data backup included in strategy
-
Configuration backup maintained
Compliance Requirements
Audit Preparation
-
Access logging enabled
-
Change tracking configured
-
Compliance policies defined
-
Documentation standards established
Data Protection
-
GDPR compliance verified (if applicable)
-
Data retention policies defined
-
Privacy controls implemented
-
User consent documented
Checklist Summary
Before proceeding with Team Member setup, verify:
- SUPER permissions available
- Team Member licenses obtained
- Azure AD users exist
- Municipal dimensions configured
- Permission strategy defined
- User information collected
- Documentation prepared
- Training plan ready
- Performance requirements assessed
- Compliance requirements met