starred/CIPP

Fork 0

mirror of https://github.com/KelvinTegelaar/CIPP.git synced 2026-04-25 08:16:01 +03:00

[GH-ISSUE #4718] [Feature Request]: Show Customer namen in tenant invitation dashboard #2198

New issue

Closed

opened 2026-03-02 13:50:23 +03:00 by kerem · 6 comments

kerem commented

2026-03-02 13:50:23 +03:00

Owner

Originally created by @jdejong-ntnt on GitHub (Sep 29, 2025).
Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4718

Originally assigned to: @Zacgoose on GitHub.

Please confirm:

I have searched existing feature requests (open and closed) and found no duplicates.
**me or my organization is currently an active sponsor of the product at the $99,- level.

Problem Statement

At the moment, when creating a new invitation / onboarding a new tenant, the links are created as shown in the image below:

For better visibility it would be of great help if we can add a 'name' or 'identifier' field when creating the invitation link so it is shown at the overview page with a customer or identifier field, so we know which invitation is sent to which customer.

Benefits for MSPs

With the extra field we as MSP can keep track of which invitation is send to who / which company. So we know where we are in the onboarding process.

Value or Importance

Of course this is not critical, but it will help the MSP in their daily business

PowerShell Commands (Optional)

No response

Originally created by @jdejong-ntnt on GitHub (Sep 29, 2025). Original GitHub issue: https://github.com/KelvinTegelaar/CIPP/issues/4718 Originally assigned to: @Zacgoose on GitHub. ### Please confirm: - [x] **I have searched existing feature requests** (open and closed) and found no duplicates. - [x] **me or my organization is currently an active sponsor of the product at the $99,- level. ### Problem Statement At the moment, when creating a new invitation / onboarding a new tenant, the links are created as shown in the image below: <img width="1882" height="338" alt="Image" src="https://github.com/user-attachments/assets/74502077-94f1-4c00-b647-481725283304" /> For better visibility it would be of great help if we can add a 'name' or 'identifier' field when creating the invitation link so it is shown at the overview page with a customer or identifier field, so we know which invitation is sent to which customer. ### Benefits for MSPs With the extra field we as MSP can keep track of which invitation is send to who / which company. So we know where we are in the onboarding process. ### Value or Importance Of course this is not critical, but it will help the MSP in their daily business ### PowerShell Commands (Optional) _No response_

kerem

2026-03-02 13:50:23 +03:00

closed this issue
added the
Feature
label

kerem commented

2026-03-02 13:50:24 +03:00

Author

Owner

@Zacgoose commented on GitHub (Sep 29, 2025):

An internal reference is what your wanting? Being able to add notes after the fact as well is likely needed so when creating links in bulk it's still useful.

@Zacgoose commented on GitHub (Sep 29, 2025): An internal reference is what your wanting? Being able to add notes after the fact as well is likely needed so when creating links in bulk it's still useful.

kerem commented

2026-03-02 13:50:24 +03:00

Author

Owner

@jdejong-ntnt commented on GitHub (Sep 29, 2025):

Yes, internal reference, nothing special...someting like below (example), just to understand when you have e.g. 10 invitations, and you only did 5 of them, you would be able to see the customers for which the invite is created, so you know which ones are left to do....
(hope it's clear?)

@jdejong-ntnt commented on GitHub (Sep 29, 2025): Yes, internal reference, nothing special...someting like below (example), just to understand when you have e.g. 10 invitations, and you only did 5 of them, you would be able to see the customers for which the invite is created, so you know which ones are left to do.... (hope it's clear?) <img width="2249" height="338" alt="Image" src="https://github.com/user-attachments/assets/6e3f02a0-a9e9-4336-85ce-50e1699d75dc" />

kerem commented

2026-03-02 13:50:24 +03:00

Author

Owner

@Zacgoose commented on GitHub (Sep 29, 2025):

Sounds good!

@Zacgoose commented on GitHub (Sep 29, 2025): Sounds good!

kerem commented

2026-03-02 13:50:24 +03:00

Author

Owner

@Zacgoose commented on GitHub (Sep 29, 2025):

I would like to work on this please!

@Zacgoose commented on GitHub (Sep 29, 2025): I would like to work on this please!

kerem commented

2026-03-02 13:50:24 +03:00

Author

Owner

@github-actions[bot] commented on GitHub (Sep 29, 2025):

Great! I assigned you (@Zacgoose) to the issue. Have fun working on it!

@github-actions[bot] commented on GitHub (Sep 29, 2025): Great! I assigned you (@Zacgoose) to the issue. Have fun working on it!

kerem commented

2026-03-02 13:50:24 +03:00

Author

Owner

@jdejong-ntnt commented on GitHub (Sep 29, 2025):

Great to see the enthusiasm on this request!
Let me know in case I can be of any help!

@jdejong-ntnt commented on GitHub (Sep 29, 2025): Great to see the enthusiasm on this request! Let me know in case I can be of any help!

No milestone

No project

No assignees

1 participant

Notifications

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

starred/CIPP#2198

No description provided.

Rows
Columns