Skip to main content

Let Issuers Control Login Requirements for Credential Sharing

Feature Request

Allow issuers to decide whether recipients must create an account and log in before sharing a credential, including adding it to LinkedIn. This would let issuers choose between additional verification and a simpler recipient sharing experience.

Posted by Vik ·
Status: Completed4 comments

Log in to comment and vote

Comments4

  • Niko Fastman

    •

    Jul 17

    •

    Merged request

    •

    1 vote

    why sign in and create an account to be able to share on linkedin?

    • Gaurav

      Team•

      Jul 4

      It is gated behind a login to ensure only the owner of the credential can add it to LinkedIn. Otherwise, anybody with access to the credential link can potentially add it to their LinkedIn profile.

      Let me know if you have any questions.

      • Niko Fastman

        •

        Jul 5

        Regarding the security concern, even if someone else were to add a credential to their own LinkedIn profile, it would be immediately obvious that the credential does not belong to them because the name on the credential would not match the LinkedIn profile. In practice, this risk seems limited compared to the additional friction introduced by mandatory sign-in.

        Is there any possibility of making LinkedIn sharing available without requiring users to create an account and log in?

        • Vik

          Team•

          Jul 9

          Hi Niko, yes, you are right that when the credential clearly contains the recipient’s name, it becomes easier to identify if someone adds a credential that does not belong to them.

          However, there are also cases, such as badges, where the recipient’s name may not be shown directly on the badge design. In those cases, requiring sign-in helps reduce misuse.

          That said, based on your feedback, we have decided to give issuers the option to choose whether recipient login should be required before adding a credential to LinkedIn. We are planning to pick this up in Q3 2026 and will update this post once we start working on it.