> For the complete documentation index, see [llms.txt](https://doj.secondliferp.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doj.secondliferp.com/legislation/doj-legislation/department-of-justice-public-legislation/case-laws/garrity-v.-new-jersey-1967.md).

# Garrity v. New Jersey (1967)

Also known as Garrity Rights refers to the protection to public employees from being compelled to incriminate themselves during investigatory interviews conducted by their employers.

Garrity rights ensure that any statement made under the threat of job loss cannot be used against the employee in criminal proceedings.

Key Points:

* Garrity rights apply only to the public employees, such as Peace Officers or other government workers.
* An employee can be required to answer questions during a internal investigation if they are made aware they are immune from criminal prosecution related to their statement.

When do they apply?

* They must be answering questions as part of their employment
* Refusal to comply could lead to disciplinary action or termination


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://doj.secondliferp.com/legislation/doj-legislation/department-of-justice-public-legislation/case-laws/garrity-v.-new-jersey-1967.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.