---
title: "Use Hyperlinks for Access and Automation"
canonical: "https://help.agiloft.com/space/HELP/43715001/Use+Hyperlinks+for+Access+and+Automation"
format: markdown
---
You can use hyperlinks to provide access to Agiloft CLM and automate actions, such as opening records, applying field values, and more. The most common use case is creating hotlinks, encrypted hyperlinks that allow secure, direct access to Agiloft CLM. For example, you can create and encrypt a hotlink that logs a user in to Agiloft CLM, creates a new record, sets a field in the record to a certain value, hides the user interface so the user doesn’t realize they entered your KB, and returns them to a URL of your choosing when they save the record. Hotlinks can also execute complex functions, such as logging in to a specific table, running a saved search, and more. 

You can embed hotlinks in emails from within your KB and have them generated at runtime, or you can generate them manually and use the links outside of Agiloft CLM. To ensure hyperlinks are secure, always use encryption and user authentication. For instructions on encrypting hyperlinks, see [Manually Encrypting Hyperlinks](#manually_encrypt_hyperlinks) below. System-generated hotlinks are automatically encrypted.

# Autologin Hotlinks

You can create a hyperlink that logs a guest user in and takes them to any screen, such as a New User form or New Ticket form without showing them the full user interface. Power users can create their own hyperlinks to take them to different saved searches, different tables, and so on. For details on constructing advanced links, see [Hyperlink Syntax and Examples](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43718366).

# > Macro (anchor)

Manually Encrypting Hyperlinks

You can create hotlinks manually for use in action buttons or outside the system, but they are not automatically encrypted. Instead, links that you create manually must also be encrypted manually. We highly recommend encrypting any of these links you create; otherwise, all the system information you include in the hyperlink construction will remain visible in the text of the link.

After you create hyperlinks, follow these steps to manually encrypt them:

1. Go to **Setup > Access > Automatic Login Hotlinks**.
2. Select any groups to exclude from using the hotlink.
3. Enter the hotlink in the Encrypt Hotlink box.
4. Select an expiration time for the hotlink, after which the hotlink will no longer work.
5. Click Encrypt. The newly encrypted hotlink then appears in the Encrypted Hotlink box. You can copy and paste the link as needed.

> ℹ️ **Example**
> ℹ️ 
> ℹ️ Imagine you enter the following hotlink:
> ℹ️ 
> ℹ️ `http://localhost:8080/gui2/login.jsp?keyID=0&KB=TESTKB&user=admin&passwd=testpassword&state=Main`
> ℹ️ 
> ℹ️ In this example, you can clearly derive the username "admin" and password "testpassword" from the link. After clicking Encrypt, the system encrypts the sensitive portions of the link and generates an output like the following:
> ℹ️ 
> ℹ️ `http://localhost:8080/gui2/login.jsp?p=a&genhotlink=Aj3ze1x9W5xwlXRB/MPL8VHo+m72uHf350nT13m+vhPCU41hVmkMfVVj/YGTEbLYYfHpv6Y`

# Hotlink Examples

Log in to Demo in Progress KB to self-register and create a New Customer record without seeing the rest of the UI:

```xml
<a href="http://www.example.com:8080/gui2/login.jsp?keyID=0
&user=register&password=register
&project=Demo%20in%20Progress&state=New:contacts.customer&
Table=Contacts&GUI=No/eui"> http://www.example.com:8080/gui2/login.jsp?keyID=0&user=register
&password=register&project=Demo%20in%20Progress
&state=New:contacts.customer&Table=Contacts
&GUI=No/eui</a>
```

Log in to Podaac KB as the FAQ user to the end user interface:

```
<a href="http://www.example.com:8080/gui2/login.jsp?KeyID=0
&project=podaac&user=faquser&password=faquser
&State=enduser"> http://www.example.com:8080/gui2/login.jsp?KeyID=0&
project=podaac&user=faquser&password=faquser
&State=enduser</a>
```

Log in to Fictional KB as a guest user to submit a new bug report:

```xml
<a href="http://www.example.com:8080/gui2/login.jsp?keyID=0
&user=guest&password=notreal&project=Fictional
&state=New:c_bugreport"> http://www.example.com:8080/gui2/login.jsp?keyID=0
&user=guest&password=notreal&project=Fictional
&state=New:c_bugreport</a>
```

For an example that uses hotlinks to access Agiloft CLM from a portal, see [Integrating Hotlinks with a Portal](https://agiloft-public.atlassian.net/wiki/spaces/HELP/pages/43715003).

# Defining the Table in a Hyperlink

Find the table value for a hyperlink by navigating to **Setup > Tables**, choosing a table, and clicking Edit. On the first tab of the wizard after the labels, you'll see the logical table name to use in hyperlinks.  
> Macro (inline-media-image)



#### Related articles

> Macro (contentbylabel)