Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[Feature Request]: Aliasing Tenant Names For Search Purposes #3035

Open
ngt-jt opened this issue Jan 7, 2025 · 8 comments
Open

[Feature Request]: Aliasing Tenant Names For Search Purposes #3035

ngt-jt opened this issue Jan 7, 2025 · 8 comments
Labels
enhancement New feature or request no-activity no-priority

Comments

@ngt-jt
Copy link

ngt-jt commented Jan 7, 2025

Description of the new feature - must be an in-depth explanation of the feature you want, reasoning why, and the added benefits for MSPs as a whole.

I'd like to propose a new feature for CIPP that would allow us to create aliases for tenant names, significantly enhancing our search functionality and overall user experience. This feature would enable us to assign custom, easily recognizable names or tags to our managed tenants, which we could use alongside the official tenant names when searching or filtering within the CIPP interface.

The proposed feature would work as follows:

  1. Alias Creation: We would have the ability to add one or more aliases to each tenant we manage. These aliases could be set up during tenant onboarding or added/modified later through a dedicated interface.
  2. Search Integration: The CIPP search function would be enhanced to include these aliases in its search parameters. When we perform a search, the system will look for matches in both the official tenant names and our custom aliases.
  3. Display Options: In list views and search results, the system could display both the official tenant name and the alias, with options to customize which is shown more prominently.
  4. Bulk Operations: The ability to apply aliases in bulk, perhaps through CSV import or a batch editing interface, would be included to facilitate easy setup, especially for those of us managing numerous tenants.
  5. Alias Categories: We could have the option to categorize aliases (e.g., by industry, location, or service level) for even more refined searching and sorting capabilities.

Reasoning:

  1. Improved Efficiency: Many of us manage dozens or even hundreds of tenants. Official tenant names are often long, complex, or similar to each other, making quick identification challenging. Custom aliases would allow for faster, more intuitive tenant location and management.
  2. Enhanced Organization: Aliases can be used to group or categorize tenants in ways that make sense to our operational structure, improving overall organization and workflow.
  3. Reduced Errors: By using clear, recognizable aliases, we can significantly reduce the risk of working on the wrong tenant due to similar names, enhancing accuracy and security.
  4. Better Client Communication: Aliases can be set to match how we internally refer to clients, aligning the CIPP interface more closely with our day-to-day operations and communication.

Benefits:

  1. Time Savings: Faster tenant identification and access translate directly into time savings, especially for those of us managing large numbers of clients.
  2. Improved Service Quality: With reduced risk of errors and faster access to the correct tenant, we can provide more efficient and accurate service to our clients.
  3. Scalability: As we grow and add more tenants, a robust aliasing system will help maintain our operational efficiency and organization.
  4. Customization: The ability to create custom aliases allows us to tailor CIPP to our specific needs and preferences, enhancing overall usability.
  5. Reporting and Analytics: Custom aliases could be incorporated into reporting features, allowing for more intuitive and meaningful data analysis and presentation.

PowerShell commands you would normally use to achieve above request

No response
@ngt-jt ngt-jt added enhancement New feature or request no-priority labels Jan 7, 2025
@KelvinTegelaar
Copy link
Owner

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 prioritize improvements that directly benefit those actively supporting CIPP and ensure we can sustain our development and support.

When a sponsor makes a feature request, their support covers training, development, documentation, and security checks. Allowing non-sponsor requests could lead to a backlog that would slow down updates and stretch resources thin, ultimately impacting the quality and sustainability of CIPP.

While we’ve closed this request, we appreciate your input, and you’re always welcome to participate in ongoing discussions or contribute to open issues. If you are a developer yourself, feel free to create a PR that includes your feature request or type "I'd like to work on this!" to assign the issue to yourself.

Did you get this notification in error? Reply with a screenshot of your sponsorship payment and we'll reopen the issue.

Thank you for understanding,
The CIPP Team

@ngt-jt
Copy link
Author

ngt-jt commented Jan 7, 2025 via email

@MWGMorningwood
Copy link
Contributor

NetGain Technologies is a sponsor of CIPP....

You might want to mark the sponsorship public so that maintainers can see that you are when submitting requests.
If it is an org sponsorship, you can display the org membership publicly as well.

@ngt-jt
Copy link
Author

ngt-jt commented Jan 7, 2025 via email

@ngt-jt
Copy link
Author

ngt-jt commented Jan 7, 2025 via email

@JohnDuprey
Copy link
Collaborator

Sponsoring as org: NetGainIT

@JohnDuprey JohnDuprey reopened this Jan 7, 2025
@github-actions GitHub Actions
Copy link

This issue is stale because it has been open 10 days with no activity. We will close this issue soon. If you want this feature implemented you can contribute it. See: https://docs.cipp.app/dev-documentation/contributing-to-the-code . Please notify the team if you are working on this yourself.

@Zacgoose
Copy link

This would be a great addition if this was added to the alert data as well, our PSA would be able to correctly connect the email with the client based on this tag/alias

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
enhancement New feature or request no-activity no-priority
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
5 participants
@MWGMorningwood @JohnDuprey @KelvinTegelaar @Zacgoose @ngt-jt