My WebLink
|
Help
|
About
|
Sign Out
Home
Browse
Search
02-09-26-WS
ArdenHills
>
Administration
>
City Council
>
City Council Packets
>
2020-2029
>
2026
>
02-09-26-WS
Metadata
Thumbnails
Annotations
Entry Properties
Last modified
2/17/2026 11:22:22 AM
Creation date
2/17/2026 11:17:15 AM
Metadata
Fields
Template:
General
There are no annotations on this page.
Document management portal powered by Laserfiche WebLink 9 © 1998-2015
Laserfiche.
All rights reserved.
/
144
PDF
Print
Pages to print
Enter page numbers and/or page ranges separated by commas. For example, 1,3,5-12.
After downloading, print the document using a PDF reader (e.g. Adobe Reader).
View images
View plain text
Mayors may wonder what right of access they themselves have to data that <br />Minn. R. 1205.0400, subp.2. <br />isn't public. Whether a mayor, council member, or staff, the law says that <br />Minn. R. 1205.0600, subp. 2. <br />access is limited to individuals "whose work assignments reasonably require <br />See Chapter4, Section 1-B-1. <br />access." Whether the mayor falls into that legal description is a question for <br />each city to decide with the help of the city attorney because it likely depends <br />on the specific situation. For this reason, mayors shouldn't be surprised if they <br />don't get a key to the city offices just because the mayor of another city does. <br />And of course, there's always a difference between whether one can access <br />private or confidential data and whether one should. <br />Since the data a person collects, creates, receives, maintains, or disseminates <br />in the capacity of mayor is government data, a mayor must exercise caution <br />about where that data is created, collected, etc. Government data can easily, <br />even accidentally, be created at home that is both public and subject to a <br />retention schedule. Also, mayors may wish to take care in what they say in <br />their official capacity within a -mails and even text messages. <br />Minn. Stat. § 13.601, subd. 2. <br />The MGDPA states that correspondence between individuals and elected <br />DPO 97-002 (Jan. 15, 1997) <br />officials is private —though either party may make it public. However, <br />and DPO 97-014 (Apr. 1, <br />1997). <br />correspondence between elected officials and city employees is public unless it <br />contains information specifically classified as non-public. This even applies to <br />Minn. Star. § 13.393. <br />the city administrator's status reports to the city council. The attorney -client <br />privilege, however, would apply to documents created for the purpose of <br />giving legal advice, such as a letter between the city attorney and a city official. <br />Minn. Stat. § 13D.05. <br />The Open Meeting Law doesn't allow the closing of a meeting solely to discuss <br />private data (except in limited circumstances clearly listed in the statute), and <br />provides that private data may be discussed openly at any public meeting <br />without fear of liability or penalty as long as the release of the data is <br />reasonably necessary to conduct the business the data relates to. If private <br />data needs to be discussed at a public meeting, it is recommended that the <br />city try to protect the information by assigning numbers, letters, or similar <br />designations to it, and that those designations be used instead of the actual <br />data. <br />Discussing private data in a closed meeting does not change the fact that it is <br />private. Therefore, even though an open meeting might have just occurred in <br />which private data was discussed, that data shouldn't be discussed with family, <br />friends, or the media as if it is now public information. <br />While in most cases private data may be discussed in an open meeting without <br />fear of liability, mayors should remember the seven situations mentioned in <br />the previous section in which the Open Meeting Law requires a meeting to be <br />closed. <br />Minnesota <br />Mayors Chapter 1-11 <br />Association <br />
The URL can be used to link to this page
Your browser does not support the video tag.