Make it much easier to invite the whole company

To increase the usefulness of GitLab we can maybe leverage the LDAP connection.

Two ideas:

1. Make an 'invite all LDAP entries' button that sends everyone an email.
2. Add all LDAP entries to autosuggest and email them when they are mentioned.

@dzaporozhets @JobV

Make an 'invite all LDAP entries' button that sends everyone an email.

I wonder who would use this. I suppose that the LDAP group you have added knows about the instance. They can simply sign in.

Add all LDAP entries to autosuggest and email them when they are mentioned.

I'm not sure I understand. From what I think you mean, this is not a good idea. This means that they could get info from projects they shoudln't have access to: "Jane mentioned you in secrets / super_secret", even if it's accidental.

Besides that, it's not uncommon to have a LDAP with 10k+ members.

Maybe we should make it possible to just mention people by email if they don't have an account yet.

@@job@gitlab.com for instance.

Why would you want to invite people when you can configure gitlab to create users automatically on their first ldap login?

@megamorf usually a GitLab instance is started somewhere in an organisation by a small group of engineers. Spreading the knowledge of the instance within the organisation is something we can work on making easier and more accessible.

That doesn't really answer my question - what's the benefit of having a bulk invite function in Gitlab when you can just send an email to all members of your organisation with a link to the Gitlab sign-in page (which then automatically creates an account for them on the first ldap-based login)?

@megamorf That would be a valid alternative to use. I'm not sure it is always easy to email everyone this way, sometimes it might not be set up.

Just keep in mind that a bulk invite for all LDAP entries would include VIPs like CEOs, CIOs, CTOs, etc. which usually shouldn't receive this sort of stuff.

@megamorf Yes, it is risky, it would be an admin only feature.

Hi @sytses,

First of all, thank you for raising an issue to help improve the GitLab product. We're sorry about this, but this particular issue has gone unnoticed for quite some time. To establish order in the GitLab-CE Issue Tracker, we must ensure that every issue is correctly labelled and triaged, to get the proper attention.

This issue will be closed, as it meets the following criteria:

• No activity in the past 4 months
• Unlabelled
• Unassigned
• It's not associated with a particular milestone

We'd like to ask you to help us out and determine whether this issue should be reopened.

If this issue is reporting a bug, please can you attempt to reproduce on the latest version of GitLab or GitLab.com, to help us to understand whether the bug still needs our attention.

If this issue is proposing a new feature, please can you verify whether the feature proposal is still relevant.

Thanks for your help

Added ~761915 label

Status changed to closed

mentioned in merge request !14785