user was created without invite may i know the reason ???

[MURUGESH S]

user was created without invite may i know the reason for that i have check the audit log and shows empty 

what is the issue can anyone help

[MURUGESH S]

.

[Trudy Claspill]

Hello @MURUGESH S 

What audit log exactly are you viewing?

Are you the only person with administrative access to your organization?

What are the User Access Settings for your product? Check the settings for Approved Domains and User Invites.

Have you set projects in your Jira instance to allow Public access?

[MURUGESH S]

Audit Log User Created shows System as Author

[MURUGESH S]

yes we have two admins in our org

[MURUGESH S]

Not allow public access

[Trudy Claspill]

How did you navigate to the Audit Log, exactly?

Your post tags indicate you are using the Free Cloud version. In the Free Cloud version, the Audit Log within the Jira product is not an available option. And the Audit Log available for the Organization (in admin.atlassian.com) requires an Atlassian Access subscription.

[MURUGESH S]

yes we have premium subscription but I'm raise this issse in other instant.

[MURUGESH S]

admin console-----> system------>auditlog

[MURUGESH S]

in confluence : Audit Log User Created shows System as Author

in JIRA : Audit Log User Created shows JIRA as Author

[Trudy Claspill]

Looking at the Audit Log within the Jira Cloud product on a paid subscription I also see that issue creation entries show "System" as the User for the activity.

I have worked only with Free Cloud products and Cloud Products that are under an Organization that includes an Atlassian Access subscription. The Access subscription provides access to an Audit Log at the Organization level which gives more information about Organization level activities like User management.

The product is getting the user information from the Site and Organization under which the Product exists. I suspect that from the perspective of the Jira product it is the "system" that is telling it to create the user, because that information is coming from the Organization/Site. I think you would need to look at the User information available at the Site/Organization level to learn more about how that user got created.