Personal Connections

A Personal Connection is a Connection that belongs to you rather than to a Tenant. You create it yourself, you are the only person who can change it, and it travels with you when you switch Tenant.

Personal Connections exist so that you can set up your own reporting against a system you have credentials for, without needing a Tenant Admin to create a shared Connection on your behalf. In exchange for that freedom they are deliberately limited: they can only be used by ReportMagic, only in Report Schedules that you created yourself, and only where the report reads and writes inside your own My Files area.

How a Personal Connection differs from a Tenant Connection

	Tenant Connection	Personal Connection
Owned by	The Tenant	You, the user
Created and edited by	Tenant Admins	Only you, its owner
Visible to	Everyone in the Tenant	Only you (and Super Admins, read-only)
Managed from	The Connections page	The Personal Connections page
Usable by	ReportMagic, AlertMagic, ConnectMagic and DataMagic	ReportMagic only
Usable in	Any Report Schedule in the Tenant	Only Schedules you created, reading and writing inside My Files
When you switch Tenant	Stays behind - it belongs to that Tenant	Comes with you - it belongs to you
Connection Roles apply	Yes	No - ownership is the only rule that matters

A Personal Connection never appears on the Tenant Connections page, and a Tenant Admin cannot see it, edit it or use it.

Managing your Personal Connections

Your Personal Connections are managed at /connections/personal. You can get there in two ways:

• From the Personal Connections card on your Profile page, using the Manage Personal Connections link. The card also lists the Connections you already have, so you can see them at a glance.
• From the Connections menu in the Admin app, by choosing Personal.

The page is available from whichever Magic Suite app you happen to be in, because your Personal Connections are not tied to any one app or Tenant.

The table shows the following columns:

• Status - whether the Connection last checked out as working. Click the indicator to check it again immediately.
• Version - the version of the remote system, where that system reports one.
• Last Checked - when the status was last collected, or Never if it has not been checked yet. Status is collected automatically once a day.
• Name - the name you use to refer to the Connection from a macro.
• Type - the kind of system being connected to. This is fixed once the Connection has been created.
• URL, User Name, Password and Additional Configuration - the connection details, exactly as for a Tenant Connection.
• Description - your own note about what the Connection is for.
• Read Only - prevents the Connection being used by macros that would write to the remote system.
• ReportMagic Access - whether ReportMagic may use this Connection at all.
• Credentials Expiry - the date the credentials are known to expire, so that you can be reminded before they do (coming in version 4.6, see below).

Use the Create, Edit and Delete buttons on the toolbar, or double-click a row to edit it.

Credentials Expiry Reminders (coming in version 4.6)

If you set a Credentials Expiry date on a Personal Connection, you are emailed a reminder 30 days, 7 days and 1 day before that date, so that you can renew the credentials before your reports start to fail. The 7-day and 1-day reminders are sent with high priority.

Reminders go out once a day, shortly after 00:15 UTC. If several of your Personal Connections are due a reminder on the same day, they are listed together in one email. Reminders are sent only to you: Tenant Admins are never told about your Personal Connections.

Personal Connections follow you across Tenants - but My Files does not

This is the single most surprising thing about Personal Connections, so it is worth stating plainly.

A Personal Connection belongs to you, so when you switch Tenant it is still there, with the same name and the same credentials. Your My Files area, however, belongs to you within a Tenant, so it is different in each Tenant.

The consequence is that the same Personal Connection, used from a Schedule in Tenant A and from a Schedule in Tenant B, will read and write two different file areas. The Connection is the same; the files are not. If you cannot find the output of a report you are sure you ran, check which Tenant you were in when you ran it.

ReportMagic only

A Personal Connection can only ever be used by ReportMagic. AlertMagic, ConnectMagic and DataMagic cannot use one.

This is why the Personal Connections page offers a single ReportMagic Access toggle, where the Tenant Connections page offers four. The other three application access toggles are not hidden or disabled - they are simply not applicable, so they are not shown.

The rule is enforced by the API as well as by the screen. If something attempts to grant one of the other applications access to a Personal Connection, the request is rejected with 400 Bad Request:

A personal Connection can only be used by ReportMagic. The following must not be set: AlertMagicHasAccess, ConnectMagicHasAccess, DataMagicHasAccess. Use ReportMagicHasAccess to permit or deny ReportMagic access.

How to resolve it: do not set those properties. If you need a Connection that AlertMagic, ConnectMagic or DataMagic can use, it must be a Tenant Connection - ask a Tenant Admin to create one.

If you are creating a Connection through the API and omit the essentials, you will also see:

A personal Connection requires both a Name and a Discriminator.

How to resolve it: supply both the Name and the Discriminator (the Connection type). The screen always sends both, so this only arises when calling the API directly.

Using a Personal Connection in a Report Schedule

You use a Personal Connection from a macro exactly as you would a Tenant Connection - by name, for example [LogicMonitor.Connection:name=myPersonalConnection].

Two conditions must both be met for the Schedule to be allowed to use it:

1. The Report Schedule must have been created by you, the owner of the Connection.
2. The Schedule's input and output paths must both be inside My Files.

The Library is deliberately not permitted. A Personal Connection holds credentials that only you are entitled to use, and anything written to the Library is visible to the whole Tenant, so allowing it would leak the results of your private credentials to other people. If you need a report in the Library, it must use a Tenant Connection.

When these conditions are not met, the macro raises an error. The report itself continues or stops according to your existing error handling settings - a Personal Connection problem does not automatically abandon the whole Schedule.

The Schedule was created by someone else

The personal Connection 'MyConnection' is not owned by the creator of Schedule 'My Schedule', so it cannot be used by it. A personal Connection can only be used by its owner.

How to resolve it: either run the report from a Schedule that you created yourself, or replace the Personal Connection with a Tenant Connection that everyone is entitled to use. Note that this includes Schedules that you now maintain but that someone else originally created - it is the recorded creator that counts.

The input or output is outside My Files

The personal Connection 'MyConnection' cannot be used by Schedule 'My Schedule'. A personal Connection can only be used by a Report Schedule whose input and output are both inside /My Files. This schedule's output path is outside it.

The final sentence names whichever path is at fault - input and output paths are, input path is, or output path is.

How to resolve it: move the Schedule's input template and its output folder into My Files, or switch to a Tenant Connection. A path such as /Library/Reports will always fail this check.

The Schedule has no usable creator

Two related messages can appear where the Schedule's creator cannot be established:

Report Schedule #123 has no recorded creator, so personal Connections cannot be used by it.

The creator of Report Schedule #123 ('someone@example.com') could not be resolved to a user, so personal Connections cannot be used by it.

How to resolve it: these normally mean the Schedule predates the creator being recorded, or was created by a user who has since been deleted. Re-create the Schedule under your own account, or use a Tenant Connection.

The entitlement could not be checked

The personal Connection entitlement for this Schedule could not be determined.

How to resolve it: this is a deliberate fail-safe - if Magic Suite cannot confirm that you are entitled to use the Connection, it refuses rather than guesses. It usually indicates a transient problem. Run the Schedule again, and raise a support request through the Feedback form if it persists.

Name conflicts

Because a macro refers to a Connection by name, a Personal Connection and a Tenant Connection sharing the same name and type would be ambiguous. Magic Suite prevents this in two places.

When you save (409 Conflict)

You cannot give a Personal Connection the same name and type as a Tenant Connection you can see. Attempting to do so - whether creating a new Connection or renaming an existing one - fails with 409 Conflict:

A Connection with the name Production and type LogicMonitor already exists as a tenant connection. Please choose a different name to avoid ambiguity.

You also cannot have two Personal Connections of your own with the same name and type:

You already have a personal Connection named Production of type LogicMonitor.

How to resolve it: choose a different name. A name that makes the ownership obvious, such as MyLogicMonitor, avoids the problem entirely. Note that the same name is perfectly acceptable on Connections of different types.

When a report runs

The check when you save covers the Tenant Connections that exist at that moment. A Tenant Admin may afterwards create a Tenant Connection that collides with your Personal Connection, or you may switch to a Tenant where such a Connection already exists. In that case the clash is caught when the report runs:

Ambiguous Connection: both a personal and a tenant LogicMonitor Connection named 'Production' exist. Please rename the personal Connection to resolve the conflict.

How to resolve it: rename your Personal Connection, as the message suggests, and update any macros that referred to it by the old name. Magic Suite deliberately does not choose one Connection over the other, because silently picking the wrong credentials would be worse than failing.

Passwords are write-only

The password on a Personal Connection is never shown again after it has been saved - not even to you, its owner. This is by design: the password is stored encrypted, and the API strips it from every response.

When you edit a Personal Connection the password field is therefore blank. Leaving it blank keeps the existing password. You only need to type in the field if you actually want to change the password.

The same applies to any other secret held in the Connection's configuration.

Deletion

You can delete your own Personal Connections at any time from the Personal Connections page.

Personal Connections are also removed automatically when the user who owns them is deleted. There is no orphaned Connection left behind, and no way for anyone else to inherit one - if the work needs to outlive the person, it needs a Tenant Connection.

A Super Admin can also delete a Personal Connection, for example while cleaning up. A Super Admin can never modify one.

What a Tenant Admin sees

Nothing. Personal Connections do not appear on the Tenant Connections page, are not counted there, and cannot be edited, cloned or used by a Tenant Admin. If a user needs a Connection that the rest of the Tenant can use, the Tenant Admin must create it as a Tenant Connection in the usual way.

If a Tenant Admin does attempt to change a Personal Connection through the API, the request is rejected with 403 Forbidden:

This is a personal Connection and can only be modified by its owner.

See also

• Connecting to External Systems - Tenant Connections
• My Profile
• Connection Role Security