Aegisify Profile Settings: Control Your Subscription, Licenses, Team, Alerts, Security, and Support
Profile Settings is the account administration center for Aegisify Audit. It brings subscription status, plan access, Aegisify Application Suite licenses, organization users, personal and company information, notification policies, password security, session controls, and support tickets into one place.
Use Profile Settings to answer the administrative questions behind the platform: What plan is active? Which products are licensed? Who has access? Which domains can they see? Who receives alerts? How is the account secured? And where does support history live?
✓
Seven Areas That Keep an Aegisify Account Operational
Open each area for the high-level purpose. This public guide describes the account workflow without reproducing private account values or the authenticated application interface.
Click a stage to expand
01SubscriptionPlan + billing
02LicensesCore + suite
03Team AccessUsers + domains
04Account ProfileContact + company
05NotificationsRecipients + policies
06PasswordCredential security
07SupportTickets + history
Account Governance Sits Beside Security Scanning—It Does Not Replace It
Profile Settings governs the account and its administrative boundaries. It is not itself a vulnerability scanner, SAST engine, DAST engine, Agent sensor, or telemetry collector.
The account page controls the commercial and administrative layer around Aegisify Audit: subscription state, product licenses, organization users, assigned domains, personal and company information, notification recipients, security settings, and support requests. Those controls determine who can use the service and how the account behaves, but opening Profile Settings does not silently launch a scan or fetch WordPress evidence.
That distinction matters. A subscription can unlock protected dashboards. Licenses can authorize products in the Aegisify Application Suite. Organization roles can determine who can access which domains. Notification profiles can decide who should hear about scan activity or Critical and High findings. But scan evidence still comes from the appropriate Audit, Agent, logging, vulnerability, SAST, DAST, threat-intelligence, or product workflows.
Know Which Aegisify Audit Plan Is Active and What It Unlocks
The Subscription Details area makes the account’s current plan and status visible so users can understand which protected SaaS capabilities, target capacity, and team depth are available.
When a subscription is active, protected Aegisify Audit dashboards are unlocked for the account according to the applicable plan and user permissions. The subscription summary also identifies the billing provider used for the account so the administrative owner can understand where renewal and cancellation are being managed.
Core Audit Access
The supplied plan summary describes Starter as including Defensive and Offensive security capabilities for one target domain and one root user. It is intended for a smaller single-site operating model.
Deeper Testing and Reporting
The Professional plan expands the model with Advanced Offensive capabilities, authenticated scanning, deeper reporting, and capacity for up to three target domains.
Team and Multi-Site Operations
The Business plan adds greater team depth, branded reporting, priority support, and capacity for up to ten target domains. The supplied account example also describes two Root users and five Admin users for this plan.
Turn Subscription Entitlement Into Product Licenses for Authorized WordPress Sites
The Licenses area connects the SaaS subscription with Aegisify Core and the WordPress Application Suite without exposing raw license values in public documentation.
Download the WordPress Control Plane
The account provides access to the current Aegisify Core package. Core is the WordPress-side control plane used to register and manage supported Aegisify Application Suite products for the licensed site.
Request Licenses Within the Active Plan
The license workspace shows how many Aegisify licenses are available under the current plan. A Business account, for example, can be entitled to multiple product licenses so separate WordPress domains can be linked within plan capacity.
See Active, Inactive, and Capacity State
Each license can be reviewed for plan, status, registered email, linked-site usage, and whether additional site capacity remains. Public documentation should show only masked examples such as AEG-••••••••••••, never production license keys.
Associate the License With an Authorized Site
A license can be linked to an authorized WordPress domain such as example.com. The account view makes it clear whether a license has no domain yet, is already consuming its site allowance, or needs to be unlinked before it can be reassigned.
Control Who Can Use the Account and Which Domains They Can Reach
Team management brings role assignment and domain scoping into the same account workflow so access can follow organizational responsibilities instead of being shared through one universal login.
Create or Update a Team User
The account administrator can maintain a user’s email address, full name, credential, organization role, and assigned domains. The supported role model in the supplied page includes Root, Admin, and Member responsibilities.
Assign Domain Scope
A Root user can operate across organization-owned domains according to the account model, while other team users can be limited to selected targets such as example.com. This supports least-privilege administration for agencies, multi-site organizations, and teams with different operational responsibilities.
Activate, Deactivate, Edit, or Remove Access
User Management exposes account lifecycle controls so administrators can adjust assignments, activate or deactivate users, and remove access when responsibilities change. The current plan’s seat limits remain part of the account-governance boundary.
Keep Personal, Company, Location, and Primary-Domain Information Current
The Profile area is the source for basic contact and organization information used by the Aegisify account.
Name and Contact Details
Maintain first name, last name, full name, account email address, and phone information so account ownership and communications remain aligned with the correct administrator.
Company, Location, and Primary Domain
Maintain company name, address, city, state, ZIP/postal information, and the primary domain associated with the account. Public examples should use neutral values such as Example Company and example.com.
Give Each Recipient the Alerts and Domains They Are Responsible For
Notification Settings is recipient-specific. Each email profile can be constrained to approved domains and the events that person actually needs to receive.
An administrator can add an address such as admin@example.com, select which authorized domains apply, enable the appropriate scan and finding alerts, choose AI health-report cadence, and set session-timeout behavior when that email corresponds to an active Aegisify account user.
Session timeout can also be managed per matching account user. The supplied interface allows Root users to update timeout settings for team users, which helps align inactivity controls with the organization’s account-security policy.
Password and Session Controls Help Protect the Administrative Layer
Profile Settings includes credential and session-management controls because access to the security platform itself should be governed deliberately.
Give Support the Product, Version, Priority, and Evidence Needed to Help
The support workflow turns a general request into a trackable case associated with the Aegisify account.
Describe the Issue
Start with a clear subject and description that explains what happened, what product is affected, what you expected, and what result you observed. Avoid putting passwords, secret keys, payment data, or other unnecessary sensitive values into the ticket body.
Select the Aegisify Product and Installed Version
The product list is sourced from the Aegisify product registry and includes the broader suite, such as Audit, WAF, Shield, SEO, Backup, SiteMap, Spam, Link, Ticket, SMTP, AI, and related products. Providing the installed version helps support understand the environment being discussed.
Set an Appropriate Priority
The supplied support workflow includes Low, Medium, High, and Production Alert priority levels. Use the level that reflects actual impact so urgent production issues can be distinguished from normal questions and lower-impact requests.
Attach Useful Evidence and Track the Case
Supported files and images can be attached when they help explain the problem. After submission, the ticket history shows the ticket number, subject, product, version, priority, status, open/closed dates, whether an administrator replied, and available ticket actions.
Profile Settings Connects Commercial Access, Operational Access, Communication, and Support
The account becomes easier to manage when each administrative control has a clear job.
The Plan Defines the Account Envelope
Subscription status determines whether protected SaaS areas are unlocked and establishes the plan-level limits for targets, team depth, and advanced capabilities.
Licenses Extend Entitlement to WordPress
Aegisify Core and suite licenses connect the account’s product entitlement with authorized WordPress sites while keeping license capacity visible.
Roles and Domains Define Who Can Act
Organization access determines which people can enter the account and which sites they are responsible for, avoiding an all-users-see-all-sites operating model.
Recipient Policies Define Who Gets Informed
Approved-domain and event-specific notification profiles help direct scan, finding, report, and session-related messages to the people who need them.
Password and Session Rules Protect the Control Plane
Credential requirements and inactivity timeouts help reduce risk around access to the security platform itself.
Tickets Preserve the Support Record
Structured tickets create an auditable support history tied to product, version, priority, status, and the evidence needed for troubleshooting.
Common Questions About Aegisify Account Administration
Does opening Profile Settings run any security scans?
No. Profile Settings manages subscription, licenses, organization access, account profile information, notifications, password/session controls, and support. Vulnerability, SAST, DAST, threat-intelligence, logging, and Agent-assisted evidence collection remain separate workflows.
What happens if the Aegisify Audit subscription is canceled?
The supplied account policy states that cancellation stops future renewal and locks account access immediately. Account-owned data is retained for 14 days so the primary root account can renew before permanent deletion.
Does linking an Aegisify license automatically scan a WordPress site?
No. License linking establishes product entitlement for the authorized domain. It does not automatically start a vulnerability scan, SAST, DAST, logging collection, or telemetry session.
Can different team users be limited to different domains?
Yes. The supplied account-management workflow supports assigning domains to organization users so access can reflect the user’s role and responsibilities instead of automatically exposing every organization-owned site.
Can notification recipients receive alerts for only selected domains?
Yes. Each recipient profile can be limited to approved domains and specific categories such as scan activity, Critical/High findings, AI health reports, and session timeout behavior where the address matches an active account user.
Does changing Profile Settings change Agent telemetry permissions?
The Profile Settings content supplied for this page does not define Agent telemetry controls. Agent sensors and Telemetry Access Control belong to separate Agent-assisted workflows and should be configured there rather than inferred from account-profile settings.
Is direct support email faster than opening a ticket?
The supplied support guidance explicitly says direct email does not guarantee a faster response and recommends opening a ticket. Tickets provide product, version, priority, status, attachments, and a trackable support history.