Article Navigation
Instructions
Add a US Phone Number Policy.
This section gives information on how to add a pre-made US Phone Number policy to the Monsido scan.
From the Monsido Domain Overview, click Select Domain. The Domain Overview page opens.
Click Open on the same row as the domain name.
The Dashboard for the domain opens.
Click the Global Policies Overview button (mallet icon) on the top menu bar.
Alternatively, click on the header of the Content Policies section.
The Global Policies page opens.
Click Add new policy.
The New Policy page opens.
Click Create your own Policy. See below for examples.
For more information, see the User Guide chapter:
Assign Rule Operators.
Assign Rules.
Click Save to save the changes. A dialog box opens.
In the dialog box, enter the policy Name (required) and Note if needed and then click Save.
From the options at the top of the page, select +Add rule to the policy. Repeat the steps above to add as many rules as needed.
Click Save. The Policy List is open and the new policy is present. A Policy scan begins automatically.
Rule operators
Starts with: Policy will search for any snippet starting with the inserted text.
Contains: Policy searches for any instances of the inserted text (single word).
Contains words: Policy searches for multiple words. Use commas to separate the words.
Contains sentence: Policy searches for any instances of the inserted sentence or text.
Ends with: Policy will search for any snippet ending with the inserted text.
Equal: Policy searches for an exact match for the inserted text or value. Example: “Monsido” - match. “About Monsido” - no match.
Regex: Use regular expressions to define what should be searched for.
Note: Regular Expressions in source-code exclusions are not 100% compatible with Monsido Policies. The languages are different (Java and Ruby).
Conforms with: Use regular expressions to define the correct structure or form of the inserted value.
Less than: Find any results less than the inserted value.
Less than or equal: Find any results less than or equal to the inserted value.
Greater than: Find any results greater than the inserted value.
Greater than or equal: Find any results greater than or equal to the inserted value
(Meta header) Date age greater than: Find meta tags older than the inserted value. Choose the time interval that matches the way your meta tag dates are written.
(Meta header) Date age less than: Find meta tags younger than the inserted value. Choose the time interval that matches the way your meta tag dates are written.
CSS selector: Policy will search for the inserted CSS selector.
Rules
Page HTML: Search for text in the entire domains html.
Page URL: Set a rule for internal page URLs.
Text: Search for text excluding CSS and HTML tags.
Page title: Search for text in the page title (title is not the header).
Page title length: Define when the rule should apply for the title.
Heading text: Search for text in headers (h1,h2,h3,h4,h5,h6).
Heading text length: Define when the rule should apply header texts.
Meta header: Search for meta header tags, that matches query.
Meta header length: Define when the rule should apply for meta headers.
Link text length: Define when the rule should apply for link texts.
External link count: Define when the rule should apply for external links.
File size: Search files across selected domains.
Image size: Search for images across selected domains.
Image text: Search for images with this name.
Image text length: Define when the rule should apply for image texts.
Readability level: Search for text that is in compliance with a school degree.
Custom Examples
The Policies module can be used to find US phone numbers that are formatted in different ways.
The following example policy will scan to locate numbers that are NOT formatted in the following way: (123) 567-7890. Below are some examples of numbers that will violate the policy:
123-456-7890
123 456-7890
123 456 7890
123-4567890
To create this policy, check the RegEx, clear the Case sensitive box, and then enter the following in the Query field:
(?!\()[0-9]{3}(?!\)).*[0-9]{3}.*[0-9]{4}
For more information, see the User Guide chapter:
Note: Regular Expressions in source-code exclusions are not 100% compatible with Monsido Policies. The languages are different (Java and Ruby).
If the policy you need is difficult to create, contact Support for assistance.
Additional information
For more information, see the User Guide chapters:
Note: Regular Expressions in source-code exclusions are not 100% compatible with Monsido Policies. The languages are different (Java and Ruby).
See Monsido for Developers for documentation and advanced help files including SDK information for developers.
For further assistance, contact the Monsido support team at support@monsido.com or via the Monsido chat and help features inside the application.
Contact us:
Monsido, Powered by CivicPlus
San Diego, CA, USA
5880 Oberlin Dr,
San Diego, CA 92121, USA
Australia & New Zealand
Suite 2.04
80 Cooper St
Surry Hills, NSW 2010
Copenhagen, Denmark
Borupvang 3
2750 Ballerup, Denmark
London, UK
14 New Street
London, EC2M 4HE