Repository navigation
[Feature Request]: HaloPSA Notification as standard throughout CIPP actions #871
Description
Please confirm:
- I have searched existing feature requests (open and closed) and found no duplicates.
- **Me or my organization currently has an active subscription to the product at the €99/month level.
Problem Statement
When completing actions in CIPP, such as adding mailbox permissions, the results currently need to be manually copied, pasted, or screenshotted into the related HaloPSA ticket as a private note.
It would be useful to have a HaloPSA Ticket field on relevant CIPP actions, similar to the existing field in the Offboarding Wizard. When a ticket ID is entered, the action results should be added to that ticket as a private note instead of raising a new ticket.
This could be implemented as a standard field across relevant CIPP actions, with a system-wide setting to make the ticket ID mandatory. This would prevent technicians from completing actions without linking the work to a HaloPSA ticket and would provide a more consistent audit trail.
Benefits for MSPs
Reduces manual work and improves logging.
Value or Importance
It's nice to have, but introduces some logging standardisation in MSP teams that reduces the possibility of techs. not logging their CIPP actions against a ticket.
PowerShell Commands (Optional)
No response
Activity
github-actions commentedon Oct 10, 2026
Hello,
Thank you for your interest in improving CIPP!
To keep our development process focused and manageable, feature requests are limited to paying users. This policy helps us prioritise improvements that directly benefit those actively supporting CIPP and ensures we can sustain our development and support.
When a subscriber makes a feature request, their subscription covers training, development, documentation, and security checks. Allowing requests from non-subscribers could lead to a backlog that slows down updates and stretches resources thin, ultimately affecting the quality and sustainability of CIPP.
While we’ve closed this request, we appreciate your input. You’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer, feel free to open a PR that includes your feature request or comment "I’d like to work on this!" to assign the issue to yourself.
Already a subscriber? Subscriptions are available at https://cipp.ms/getcipp. If you subscribed through Stripe, reply with the email address you used to subscribe (or a screenshot of your Stripe receipt) so we can verify your subscription. If your organisation holds the subscription, let us know which organisation so we can match it.
Still on a legacy GitHub Sponsors plan? Make sure your GitHub account is publicly linked to the sponsoring organisation. Go to the organisation page on GitHub, select People, and ensure your membership shows as Public (not Private). If your membership is private, we won't be able to verify that you're covered by the organisation's plan.
Did you get this notification in error? Reply with a screenshot of your Stripe receipt or GitHub Sponsors payment, or your public organisation membership, and we'll reopen the issue.
Thank you for understanding,
The CIPP Team