Creating Your First Profile
Profiles connect camera triggers to skills. When you assign a profile to a group, it creates a Detection that appears in the Detections page. This guide shows you how to create a profile that activates your skill when events occur.
What You'll Create
We'll create a profile that:
- Triggers on camera motion detection
- Runs your Intruder Detection skill
- Operates during after-hours
- When assigned to a group, becomes a Detection
Prerequisites
- A skill created (see Creating Your First Skill)
- Camera(s) assigned to your group
- Understanding of your camera's trigger capabilities
Step 1: Navigate to Profiles
- Open the Anava dashboard
- Click Detections in the sidebar (or use AI Configuration > Detections)
- Click Profiles in the breadcrumb navigation
- Click + Create Profile and select your skill
Step 2: Basic Information
Fill in the profile details:
| Field | Value | Notes |
|---|---|---|
| Name | "Motion - Intruder Detection - After Hours" | Descriptive name |
| Active | Yes | Enable immediately |
Include trigger type, skill purpose, and schedule in the name for easy identification.
Step 3: Select the Skill
- In the Skill dropdown, select "Intruder Detection"
- Verify the skill details show correctly
If your skill isn't listed:
- Ensure it's in the same group
- Check it was saved successfully
- Refresh the page
Step 4: Configure the Trigger
The trigger determines what camera event starts analysis.
Choose Trigger Type
| Trigger | Use When |
|---|---|
| Motion | General-purpose, always available |
| Object | AXIS Object Analytics pre-filtered |
| DigitalInput | Physical sensors connected |
| Manual | VMS or operator initiated |
| Schedule | Continuous monitoring |
For this example, select Motion.
Motion Trigger Configuration
Motion triggers don't require additional settings. The camera's built-in motion detection will activate the profile.
For Digital Input: Specify port number (1-8) For Object: Specify AOAS scenario (person, vehicle, etc.)
Step 5: Configure View Area
Select which camera stream to capture:
| View Area | Typical Use |
|---|---|
| 1 | Default full view |
| 2-4 | Quad view channels |
| 5-8 | PTZ presets or corridors |
For most cameras, select View Area 1.
Step 6: Set Schedule (Optional but Recommended)
Limit when the profile is active to reduce unnecessary analysis.
Option 1: 24/7 (Always Active)
Leave schedule as default for continuous monitoring.
Option 2: Camera Schedule
Use schedules defined on the camera:
- Select Use Camera Schedule
- Choose from available schedules
Option 3: After Hours Only
For security use cases, configure after-hours:
- Select Custom Schedule
- Define time windows:
- Weekdays: 6 PM - 8 AM
- Weekends: All day
Step 7: Advanced Settings (Optional)
Pre-filter Model
Override the default pre-filter model if needed.
Confirmation Threshold
Set minimum confidence for ONVIF events (0-100):
- Lower = More sensitive, more false positives
- Higher = Fewer alerts, may miss detections
Default (0) uses skill-level setting.
TTS Buffer
Minimum time between voice announcements (milliseconds):
- Default: 30000 (30 seconds)
- Increase if TTS is too frequent
Step 8: Save and Activate
- Review all settings
- Click Create Profile
- Verify profile appears in list with Active status
Step 9: Test the Profile
Generate a Test Event
- Walk in front of the camera
- Wait 5-10 seconds for analysis
Verify in Sessions
- Navigate to Sessions in sidebar
- Find your test session
- Verify:
- Correct skill was used
- Objects were detected
- Questions were answered
Check VMS (If Configured)
- Open your VMS
- Check for ONVIF event from camera
- Verify action rules triggered
Understanding Your Detection
Once the profile is assigned to a group with cameras, it becomes a Detection:

The Detection appears in the Detections page, showing the profile name, group, trigger type, and linked skill.
Profile Configuration Summary
Name: Motion - Intruder Detection - After Hours
Active: true
Trigger:
Type: Motion
Skill: intruder-detection
View Area: 1
Schedule:
Weekdays: 6 PM - 8 AM
Weekends: All day
Options:
Confirmation Threshold: 0 (use skill default)
TTS Buffer: 30000ms
Common Profile Issues
Profile Not Triggering
-
Check Active status
- Profile must be Active (not disabled)
-
Verify schedule
- Current time must be within schedule
-
Check trigger type
- Motion trigger needs motion on camera
- Digital Input needs I/O signal
-
Verify camera connection
- Camera must be online in group
Wrong Skill Running
-
Check skill reference
- Verify correct skill is selected
-
Multiple profiles
- Other profiles may also match trigger
- Each matching profile runs independently
No ONVIF Events
-
Check skill configuration
- Objects must be enabled
- Objects must be stateful
-
Check detection results
- View session to see if objects were detected
- No detection = no event
Creating Additional Profiles
Once comfortable, create profiles for:
Different Triggers
- Add Object Analytics trigger for pre-filtered events
- Add Digital Input for door sensors
Different Schedules
- Business hours monitoring
- Event-specific schedules
Different Skills
- PPE compliance
- Queue monitoring
- Safety hazards
Next Steps
- Best Practices - Learn detection design patterns
- Tuning - Reduce false positives
- Multiple Profiles - Manage complex configurations
Related Topics
- Detections Overview - How profiles create detections
- Profiles Reference - Complete profile documentation
- Groups - Organizing profiles