ŁukaszBachman

Hi Kalin! Unfortunately, this is not supported yet. We don't have it on our roadmap yet either, because you are the first person asking for this by far. If more people will be interested, then I will be happy to look into this further. Translating whole application is a huge effort, and we are putting all our horsepower into delivering more reviewing features right now.

Hi Adam! This is something new for us. We will try to reproduce the issue, let's hope that it will show up in a controlled environment. Next time you see it, could you have a look at JavaScript logs to see if any errors are reported?

Hi Adam! Indexing and working on the case at the same time will be very hard to achieve. Most of our internal data structures are not tailored to be handled this way. However I understand your need and, oddly enough, this is second such request from our customers during this week. We are currently working heavily on making indexing engine faster and better, so it will be hard to add additional tasks to the pipeline there, but rest assured we will evaluate this. Please just answer me this - how would you expect it to work with regard to searching when new data is indexed constantly? Are you planning to just review & tag all documents in the data that was already present in the case? After all "look and find" keywords can very well be in the batch of data that hasn't been indexed yet so searching might not give accurate results. Would you be willing to live with that? For searching Connect is using the same date settings as Intella Desktop, but it always uses "mm/dd/yyyy" format in the UI. I'll have a look and see if this could be addressed. As to the rest of you ideas - I think all of them are valid and I'll put it on the roadmap. Thanks for those! :-)

Hi KiwiBarrister, I do not think that you will be able to export it to CSV this way. I know that adding "Parent ID" to columns is already on the roadmap, but listing attachments right beneath the containing email is not possible right now.

Hi all! Recently we started asking ourselves about what are the most popular monitor setups among our clients. Are you using single or dual monitor setup? Are you using Connect mainly on laptops, PCs or mobile devices? How big are your displays? Please help us make the Intella Connect experience better by participating in this short poll! Thank you in advance, Łukasz

Glad I could help :-) Hey, all in all PICNICs are plain fun! :-)

I think I might have a clue what's up, but please tell me this first - when you open the case in TEAM then you can properly see all the items flagged by all the users in Features Facet > Flagging node, right?

Adam, so you would be interested in a fully automated process? We thought about that, but we are curious to learn how often would you use that? If you think about it, this operation could be a bit risky. If you have a phrase "test" present in some email and an image (flat bitmap), then automated redaction might miss the image. So I assume that regardless of the level of automation, there will be always some manual work involved in order to oversee the results. Am I right?

Hi Adam! As to the first question, the flaggings should be seen in both Connect and TEAM. Please note that the flaggings are presented to the user who made them. So if users A and B have both flagged item#1, then each of them will see that item as flagged. But if only the first user has flagged an item, then the only way for user B to know about it is either by following Activity stream or by querying via Features Facet (Flagged > by user A). Does that help? Good news for you - the Exporting Permission has already been introduced and is now being tested. It will be a part of 1.7.3. New permissions mechanism allows to control who can download and export items. Do you think it should also affect printing of an item (action available in the Previewer)?

Intella tries to recover as much as it can from PSTs and OSTs. All discovered items are then placed in the special folder named . You can look up this information in Intella's Users Manual, section "9.2.2 Adding an MS Outlook file (PST, OST) source".

Hi Glenn! Recovery of deleted items is not currently supported for EnCase images. We might consider it at some point in the future. How often do you find a need for such feature? Is that something you would find useful on day-to-day basis?

Right, I overlooked the forum name :-) Anyways, it's very similar in standalone Intella. First time you see external images in a case, you should be asked if you want to fetch an external content. However in Intella you can select a "do not ask again" checkbox and you wouldn't be bothered with this dialog further. Could it be that you have chosen to ignore the images and that is why the "Show images" button is no longer showed? If so, then you can override this setting in: Menu > Preferences > Results.

Hi Adam! There are two things important to notice here: Yes, you have to call an action so that the images are fetched, because we do not show images in Connect by default. We are being restrictive here, as we would like to sensitize the user that watching external images might be a potential security risk. Thus, one will have to click on "Show images" button to see them (see attachments down below). In HTML previews we can have two types of images: internal (embedded in an email, seen as attachments by Intella) and external (included by an image body via tag). Internal images will usually always be rendered (unless they are not valid images, for some reason). However external images could have simply been removed from an external server and now cannot be fetched and shown. I hope that clarifies things, if not then please let us know. We will be glad to shed some more light on the topic.

Gmail sends out custom MBOX files as a response to a 2703(d) court orders. These MBOX files can be formatted in a non-standard way, which may cause issues when indexing with Intella. To remedy this, we have created a free utility to split a 2703d MBOX dump into a set of separate *.eml files. These files can then be indexed in Intella and reviewed in a much more efficient way. This utility is free of charge and available for download in our Knowledge base (see link down below). http://support.vound-software.com/Default/Knowledgebase/Article/View/182/79/custom-mbox-splitter---free-utility-for-2703d-gmail-dumps Kind regards, Łukasz Bachman

Hi Adam! Yeah, those are known issues with the current approach. We are thinking about starting Connect as a Windows service, which should solve most of the issues. The task is already planned on our todo-list, perhaps even for 1.7.3.

Hi Adam! Would it be enough for them to print the contents of a singular tab at a time (contents tab, raw data, actions, comments, whichever)? If so, then that would be an easy one and we would surely add it in 1.7.2! We will simply modify the way in which browser is rendering the Previewer. That should be perfect for this use case. About your feedback regarding ACLs and "roles". We had a meeting on Monday and decided to implement restrictions on Exporting as one of the first ACLs which will be added. That should be good news for you as I know your organization will benefit from it Also, we have talked about different layers of user roles (types). We have agreed that this is something we will have to implement soon, but we'll need to create mechanism flexible enough to match any organization, but very easy to grasp at the same time. This will require some more thinking and design process. Now, about the deadlines. We have reached the point where upcoming 1.7.2 release has a lot of improvements ready, so we want to push them to the end users as soon as possible. We are doing a code freeze this week, so I don't think I will be able to squeeze ACLs there. However this will be a first task for me to start 1.7.3 with, so you can expect it to be done in this release cycle. I hope those are good news for you :-)

Hi Adam, perfect, I can see the clear picture now! I will gather your use case along with similar ideas and try to come up with some solution that would satisfy all of them. Then I will present it to the rest of the staff and see if we find a room for it in the upcoming release. I'll get back to you when we make a decision.

We use the ACL abbreviation for Access Control Lists, but I guess that is what you are after as well. The idea that you have sounds familiar, as we have been talking about features like that before. We decided to start with implementation of ACLs, as this is the first step to managing layers of access in any case. I think at some point our ACLs will evolve into something similar (or the same) as you are describing. I have a few questions, though: 1. How do you divide this work between different reviewers? Is it based on custodian, volume of the data set (say, split equally 33% each), potential value of evidence (possible junk files vs. confidential docs), etc.? There can be plenty of scenarios here, I am wondering what would you need the most. 2. In your idea, are Managers essentially the same as admins? Admin can see every case and modify server settings, which of course gives him unlimited access to pretty much everything. Do you need Managers to have some less "power" in hand? For instance, manager assigned to case A cannot do the same stuff i case B, because admin did not give him access to it. I am asking about this because perhaps Managers are not really needed, and you would only need more ACLs and some nifty tool for managing them? For instance, if we added limitation saying that a given user can see only the data tagged with a given tag and then added simple wizard allowing to apply this restriction to 20 different reviewers easily, would that be enough? 3. Did you took into consideration what impact will the relationships between the items assigned to two different reviewers have? Lets say that user A is allowed to only see emails, while user B - images. If user A searches for children of some email containing attached images, do you think it should pop up in the results (since user A cannot see images due to the ACL restrictions)? Thanks for shedding a light on the topic :-)

We will also add some basic headers (from, to, topic, etc.) to the top of the email preview, so that reviewers will get all the necessary metadata in one view.

Hi all! Today I'm lifting the curtain a little bit and offering you a glimpse of how the new Previewer will look like. We have redesigned it to be cleaner and easier to work with. On attached screenshot you can also see original rendering of an HTML email. Yes, a real HTML email with styling, inline images and everything you would see in standalone email clients Enjoy!

We are thinking about rendering email threads (emails including a bunch of replies/forwards) just like web clients do with foldable (collapsible) panels. This means that if you have, say 10 replies in one thread, then we show only the most recent one expanded, and the others will be small panels, which will unfold when you click on them. This aims to reduce the effort of the reviewer to scan through all the messages that he has already seen, just to get to the previously unseen part of an email. The 2nd question seems like another type of ACLs, right? I mean the same sort of a feature that 1.7.1 release has offered while setting who has access to a given case. I think we can add it along with other types of ACLs that we are planning to include.

Starting with 1.7.1 release we decided to stop producing 32bit installers, due to the memory limitations that this architecture has. So we are only building 64bit versions.

Hey, that's good idea :-) I will arrange that. Your profile has been updated, so please check it out in some free time.

Hi all! With Intella Connect 1.7.1 officially released, we have decided to focus our efforts on implementing new features and various enhancements to the process of reviewing the data. This means that we want to give the Investigators some new and better tools, so that they can easily review more items and deliver results faster, than ever before! We have already started working on some new and exciting features, like: native rendering of HTML emails - inline images will show up inline the text; the custom styling will be preserved. load files export - Intella Connect will have the same capabilities as Intella Desktop in terms of producing various types of exports. improved thumbnails generation - will greatly reduce the time needed for fetching and showing thumbnails, making reviewing images very fast improved email threads rendering (planned) These are our main ideas for the 1.7.2 release, but we are not planning to stop there. We wish to encourage you to share your ideas with us, since we have reserved additional time for implementing features which are most crucial for you! Ask yourself this: What features would improve my experience with reviewing the data? and let us know! We will make sure to analyze each one of the ideas posted below and see if we can add it to the 1.7.2!

I think that both ideas are valid and we will definitely consider them as an extension of user access management. I very much like the idea of limiting access till particular point in time. That could be very handy in many use cases.